[v18] MWI: Allow tbot to be configured explicitly to write secrets to an external Kubernetes cluster#63037
Merged
strideynet merged 3 commits intobranch/v18from Jan 23, 2026
Merged
Conversation
strideynet
temporarily deployed
to
docs-amplify
GitHub Actions
Inactive
|
Amplify deployment status
|
timothyb89
approved these changes
Jan 22, 2026
boxofrad
approved these changes
Jan 22, 2026
Merged
1 task
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
3 participants
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.
Backport #62908 to branch/v18
changelog: Allow kubeconfig and context to be explicitly configured for
tbotkubernetes_secretdestination.