feat(cli): Add token authentication support for connect kube helper #6333
+22
−4
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Adds support for consuming password-type credentials when connecting to Kubernetes targets using
boundary connect kubehelper command.When a password credential is brokered through Boundary, the command will now pass it as a bearer token to
kubectlusing the--tokenflag.Tested with both Static and Vault credential stores against an actual Kubernetes cluster.
PCI review checklist
Examples of changes to security controls include using new access control methods, adding or removing logging pipelines, etc.
Reason for change: Enable connect kube helper to authenticate to Kubernetes clusters using credentials brokered.
Revert plan: Can be fully reverted by reverting this PR.
Security control impact: No changes to security controls. Follows existing pattern from other connect commands (SSH, Postgres, Redis).