-
Notifications
You must be signed in to change notification settings - Fork 14.5k
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
Add LegacyServiceAccountTokenCleanUp feature in alpha; move LegacyServiceAccountTokenTracking to GA #41341
Conversation
Welcome @yt2985! |
/lgtm |
LGTM label has been added. Git tree hash: 45bf8209d860369a65022c6253960c8874fe0848
|
/retitle Add LegacyServiceAccountTokenCleanUp feature in alpha; move LegacyServiceAccountTokenTracking to GA |
content/en/docs/reference/command-line-tools-reference/feature-gates.md
Outdated
Show resolved
Hide resolved
cc80fc1
to
4821cbe
Compare
[service account tokens](/docs/reference/access-authn-authz/authentication/#service-account-tokens). | ||
[service account tokens](/docs/concepts/security/service-accounts/#get-a-token). | ||
- `LegacyServiceAccountTokenCleanUp`: Clean up Secret-based | ||
[service account tokens](/docs/concepts/security/service-accounts/#get-a-token). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What does this "clean up" means to end users?
Is this really a user aware implementation change?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What does this "clean up" means to end users?
Is this really a user aware implementation change?
When this feature is default to be enabled in beta, those automatically generated service account token will be deleted if they are not been used for a time period (default to be one year). Please refer to
[KEP]: https://github.com/kubernetes/enhancements/tree/master/keps/sig-auth/2799-reduction-of-secret-based-service-account-token for the rationale and kubernetes/kubernetes#115554 for the implementation.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the clarification. I believe this clarification could be incorporated into the feature description, or else people like me may treat it as an implementation clean up rather than token clean up.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
btw, as someone who is too bandwidth limited to check the design or the source code, I'd suggest we articulate user perceivable changes clearly.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you, Qiming. I updated the feature description.
2da1b4c
to
10f2444
Compare
LegacyServiceAccountTokenTracking to GA.
/lgtm |
LGTM label has been added. Git tree hash: c60e1299671d75be7f757ba55ca150e25554e97a
|
Thanks /approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: sftim 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 |
Hey @yt2985 @zshihang , This docs PR was merged but the associated KEP was then deferred to 1.28, so I think we would want to revert this and then make the feature gates changes when this lands in 1.29? cc: @sftim Ref: Slack Discussion on this |
PR: kubernetes/kubernetes#115554
Issue: kubernetes/enhancements#2799