Improve Azure AKS Auth
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 7
- Forks
- 2
- Avg merge
- 1d 15h
- Merged PRs (30d)
- 3
Description
Currently we do some shenanigans shelling out to kubelogin in order to build a valid kubeconfig for AKS clusters using a developer's current session as created via az login
There's probably a better way that shelling out that will let use invoke the cli directly via code, or potentially not even need kubelogin. We should look into this.
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
No file or test is named; first locate the Go entry point that shells out to kubelogin and turns the developer's az login session into an AKS kubeconfig. Compare a direct Azure CLI invocation with avoiding kubelogin, then define and verify the chosen authentication path against the existing behavior. Done means AKS authentication works without the current shenanigans.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure, go, kubernetes
- Domain
- authentication, cloud
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100