-
Notifications
You must be signed in to change notification settings - Fork 38.6k
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
Store validating admission as beta #120018
Store validating admission as beta #120018
Conversation
I think we should pick this back to 1.28.1 to minimize alpha data we persist while the feature is in beta |
/lgtm |
LGTM label has been added. Git tree hash: 175ba77cb528b0a8e111b9c103dc4266b1426c48
|
I support backporting this to 1.28.1 |
/retest |
oops, had to regenerate discovery to update storageVersionHash |
cf10219
to
af9bf7b
Compare
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: jpbetz, liggitt 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 |
cc @cici37 |
#119723 flake |
This change was in the original beta promotion PR but was reverted due to comment during review concerned with upgrade interactions: |
Hmm... storing alpha data in etcd for a beta feature is unfortunate. It means that someone who never enabled the alpha would still be exposed to alpha data and reliance on alpha types. It's not as big a deal since the beta API is not enabled by default, so maybe we can limit this change to master and not backport it. |
/retest |
/test pull-kubernetes-e2e-gce |
LGTM label has been added. Git tree hash: ed157ecda72243bff5206713757bab8a6a7c6f32
|
/retest |
What type of PR is this?
/kind cleanup
What this PR does / why we need it:
Switches the storage version for validating admission policies / bindings to beta. This should have happened when the feature was promoted to beta, but got missed.
This PR also updates the etcd data test to catch this in the future (if a non-alpha version is available, expect the storage version to be non-alpha).
Does this PR introduce a user-facing change?
cc @jpbetz @cici37