MWI: Allow tbot to be configured explicitly to write secrets to an external Kubernetes cluster#62908
Merged
strideynet merged 3 commits intomasterfrom Jan 21, 2026
Merged
Conversation
|
Amplify deployment status
|
boxofrad
approved these changes
Jan 16, 2026
Contributor
boxofrad
left a comment
There was a problem hiding this comment.
One small typo, but otherwise looks great!
docs/pages/reference/machine-workload-identity/configuration.mdx
Outdated
Show resolved
Hide resolved
strideynet
commented
Jan 19, 2026
docs/pages/reference/machine-workload-identity/configuration.mdx
Outdated
Show resolved
Hide resolved
timothyb89
approved these changes
Jan 21, 2026
Contributor
|
@strideynet See the table below for backport results.
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
In some cases, users want to run
tbotexternal to a Kubernetes cluster and write artifacts to secrets within that Kubernetes cluster. Today, thekubernetes_secretdestination relies on the in-cluster configuration and credentials, which makes it awkward to use in this way.This PR allows the user to explicitly set
kubeconfig_pathandkubeconfig_contextto target a Kubernetes cluster using a kubeconfig file.Manually tested:
changelog: Allow kubeconfig and context to be explicitly configured for
tbotkubernetes_secretdestination.