reload kubeconfig auth tokens
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 10.1k
- Forks
- 413
- Avg merge
- 1d 10h
- Merged PRs (30d)
- 6
Description
Describe the Feature You Want
Some teams rotate auth credentials by writing a new kubeconfig with the new creds. Tilt should have some way to reload those credentials.
Current Behavior
Currently, Tilt loads the kubeconfig at startup, and uses that for the whole session.
Why Do You Want This?
see above
Additional context
kubectl has auth plugins that handle token expiration internally. This is how token rotation is typically handled in Kubernetes client libraries
As far as I can tell, most of the libraries Tilt uses don't have an easy way to reload the kubeconfig without throwing away everything and re-initializing from scratch. So this might be technically infeasible to implement.
Related issue: https://github.com/tilt-dev/tilt/issues/2123 (which is for the use case where the cluster itself has been reset)
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
Start by investigating how Tilt loads kubeconfig credentials and how its Kubernetes client libraries retain them for a session. Compare this with kubectl auth plugins and the related cluster-reset issue #2123. Done means establishing whether credentials can be reloaded without discarding and re-initializing the relevant state, then documenting or implementing a viable approach.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- infrastructure
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100