Frequent Device Login Prompts When Switching Regions (China and Global)
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 585
- Forks
- 127
- Avg merge
- 7d 15h
- Merged PRs (30d)
- 3
Description
I'm using kubelogin to authenticate kubectl CLI access across multiple AKS clusters in different regions (e.g., China and Europe). However, when I switch contexts between clusters in these regions, I’m frequently prompted to perform a device login for every kubectl command.
This behavior appears inconsistent with expected token caching. It seems that tokens are not being reused or cached correctly across regions or Azure cloud environments (e.g., Azure China vs Azure Global).
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 reproducing the behavior with kubelogin and kubectl while switching between AKS contexts in Azure China and Azure Global. Trace how authentication tokens are cached and selected across those cloud environments. Done means switching contexts reuses valid tokens where possible and does not prompt for device login on every kubectl command.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure, go, kubernetes
- Domain
- authentication, cli, cloud
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100