kubeconfig does not reload when changed
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 10.1k
- Forks
- 413
- Avg merge
- 1d 10h
- Merged PRs (30d)
- 6
Description
I have a tilt instance up and running with a KUBECONFIG env var set to a valid kubeconfig. I want to reset my cluster and start over from a fresh cluster so I run kubeadm reset and kubeadm init on the node. I then copy down the new /etc/kubernetes/admin.conf kubeconfig and replace KUBECONFIG local file with the contents of the admin.conf file.
Tilt now complains about an x509 error because I have regenerated the CAs which is part of the standard process of kubeadm reset and kubeadm init
I would expect tilt to reload that file and was surprised when I had to kill the process and restart it.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue provides no file or test path. Start by locating the kubeconfig loading and reload/watch entry points, then reproduce the problem by replacing KUBECONFIG after startup. Done means Tilt refreshes the configuration and avoids the x509 error without requiring a restart.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100