Skip to content

do not pollute global kubeconfig when creating a dev setup#388

Merged
xrstf merged 1 commit into
kbind-dev:mainfrom
xrstf:no-kubeconfig-pollution
Nov 18, 2025
Merged

do not pollute global kubeconfig when creating a dev setup#388
xrstf merged 1 commit into
kbind-dev:mainfrom
xrstf:no-kubeconfig-pollution

Conversation

@xrstf

@xrstf xrstf commented Nov 18, 2025

Copy link
Copy Markdown
Contributor

Summary

The k bind dev create command already spits out 2 kubeconfig files. It is unnecessary for it to also modify my fallback system-wide kubeconfig. This happens by "accident" when running kind create cluster without an explicit kubeconfig path.

This PR changes the call to kind and explicitly configures the desired kubeconfig path, so kind will not touch my ~/.kube/config anymore (me personally, I kind of rely on it being empty and defaulting to localhost:8080 for some other automation; I also hate it when I run such a command with a KUBECONFIG variable set and accidentally overwrite it with a kind kubeconfig).

What Type of PR Is This?

/kind cleanup

Release Notes

NONE

@xrstf
xrstf requested a review from a team as a code owner November 18, 2025 14:13
@xrstf
xrstf enabled auto-merge (squash) November 18, 2025 14:22
@xrstf
xrstf merged commit 21be815 into kbind-dev:main Nov 18, 2025
6 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants