-
Notifications
You must be signed in to change notification settings - Fork 39.4k
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
BoundServiceAccountTokenVolume ga #101992
Conversation
|
/triage accepted |
|
@zshihang: You must be a member of the kubernetes/milestone-maintainers GitHub team to set the milestone. If you believe you should be able to issue the /milestone command, please contact your and have them propose you as an additional delegate for this responsibility. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
|
This PR may require API review. If so, when the changes are ready, complete the pre-review checklist and request an API review. Status of requested reviews is tracked in the API Review project. |
|
|
||
| admit := NewServiceAccount() | ||
| admit.generateName = testGenerateName | ||
| admit.boundServiceAccountTokenVolume = deprecationEnabledBoundTokenVolume |
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.
this is strange... was this testing admission with bound service account tokens turned on, and expecting a non-bound-service-account-token volume?
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.
oh... no... it's testing what happens if a pod that has a secret-based volume already passes through admission. I think we want to keep this test.
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.
initially i thought it was testing getReferencedServiceAccountToken then this test is not needed any more.
as you mentioned, bound token was actually enabled in this test. looks like it just made sure existing volume at DefaultAPITokenMountPath would prevent bound token volume mounting, which is duplicate of TestRespectsExistingMount.
test/e2e/cloud/gcp/auth/service_account_admission_controller_migration.go
Show resolved
Hide resolved
|
/remove-kind api-change lgtm, one question about the upgrade test |
|
/approve |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: liggitt, zshihang 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 |
|
/test pull-kubernetes-e2e-gce-alpha-features |
|
/lgtm |
|
/retest |
|
Yes. Removal of those secrets is distinct from this feature and the plan is being worked out in kubernetes/enhancements#2800 |
|
thanks @liggitt |
What type of PR is this?
/kind feature
/kind api-change
What this PR does / why we need it:
graduate BoundServiceAccountTokenVolume to GA
Which issue(s) this PR fixes:
Fixes kubernetes/enhancements#542
Special notes for your reviewer:
Does this PR introduce a user-facing change?
Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.: