-
Notifications
You must be signed in to change notification settings - Fork 3.3k
Improve the refreshing of tokens from inside the cluster #1949
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Improve the refreshing of tokens from inside the cluster #1949
Conversation
Requests from inside the cluster misuse the API to refresh tokens. Signed-off-by: Alexis Zamanis <[email protected]>
/assign @yliaog |
thanks for the pr. is there a test to show the pr fixes the problem stated in the issue: #1948 |
@yliaog This PR fixes a design problem, rather than a bug. As explained in #1948, the code works, but the API is misused. The proposed solution properly uses the API, and brings the in-cluster code in line with the out-of-cluster code. Compare the in-cluster code: python/kubernetes/base/config/incluster_config.py Lines 95 to 100 in 392a8c1
and the out-of-cluster code: python/kubernetes/base/config/kube_config.py Lines 575 to 579 in 8f80cf4
|
thanks. /lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: AlexisZam, yliaog The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
What type of PR is this?
kind/design
What this PR does / why we need it:
Requests from inside the cluster misuse the API to refresh tokens.
Which issue(s) this PR fixes:
Fixes #1948
Special notes for your reviewer:
Does this PR introduce a user-facing change?
Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.: