Make controller clients more resilient to token changes
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 8.7k
- Forks
- 4.8k
- Avg merge
- 4d 10h
- Merged PRs (30d)
- 53
Description
Controllers are using service account tokens to make API calls for builds/deployments/replication controllers.
There are circumstances where their API tokens are no longer valid:
- Token is deleted/rotated
- Signing key is changed
Under those circumstances, the infrastructure components should be able to obtain an updated token without requiring the admin to manually delete/recreate tokens or restart the server.
Contributor guide
No contributing guide indexed for this repository
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 mapping the builds, deployments, and replication controllers that use service account tokens, then inspect how each obtains and retains credentials. Reproduce the deleted, rotated-token, and changed-signing-key cases described in the issue. Done means affected infrastructure components obtain updated tokens and resume API calls without manual token deletion or server restart.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- authentication, backend, infrastructure
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100