Skip to content

Comments

MWI: Allow tbot to be configured explicitly to write secrets to an external Kubernetes cluster#62908

Merged
strideynet merged 3 commits intomasterfrom
strideynet/explicit-kubeconfig-config
Jan 21, 2026
Merged

MWI: Allow tbot to be configured explicitly to write secrets to an external Kubernetes cluster#62908
strideynet merged 3 commits intomasterfrom
strideynet/explicit-kubeconfig-config

Conversation

@strideynet
Copy link
Contributor

In some cases, users want to run tbot external to a Kubernetes cluster and write artifacts to secrets within that Kubernetes cluster. Today, the kubernetes_secret destination 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_path and kubeconfig_context to target a Kubernetes cluster using a kubeconfig file.

Manually tested:

  • External: KUBECONFIG env var
  • External: KUBECONFIG env var and kubeconfig_context
  • External: kubeconfig_path
  • External: kubeconfig_path and kubeconfig_context
  • Internal: Default - in-cluster credentials.

changelog: Allow kubeconfig and context to be explicitly configured for tbot kubernetes_secret destination.

@github-actions
Copy link

github-actions bot commented Jan 16, 2026

Amplify deployment status

Branch Commit Job ID Status Preview Updated (UTC)
strideynet/explicit-kubeconfig-config a635988 2 ✅SUCCEED strideynet-explicit-kubeconfig-config 2026-01-19 14:27:00

Copy link
Contributor

@boxofrad boxofrad left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

One small typo, but otherwise looks great!

@strideynet strideynet added this pull request to the merge queue Jan 21, 2026
Merged via the queue into master with commit 3f3af09 Jan 21, 2026
45 checks passed
@strideynet strideynet deleted the strideynet/explicit-kubeconfig-config branch January 21, 2026 20:23
@backport-bot-workflows
Copy link
Contributor

@strideynet See the table below for backport results.

Branch Result
branch/v18 Create PR

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants