Promote apiserver.config.k8s.io/v1, kind=ResourceQuotaConfiguration#85099
Promote apiserver.config.k8s.io/v1, kind=ResourceQuotaConfiguration#85099k8s-ci-robot merged 1 commit intokubernetes:masterfrom
Conversation
3e457d1 to
11416a4
Compare
|
/retest |
11416a4 to
ac6eb7e
Compare
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: liggitt The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
ac6eb7e to
c650f69
Compare
c650f69 to
7d3012f
Compare
|
/sig api-machinery related to #76310 |
ravisantoshgudimetla
left a comment
There was a problem hiding this comment.
Thank you @liggitt for working on this :)
/lgtm
|
/hold for @deads2k ack |
| }}, | ||
| }, | ||
| { | ||
| name: "valid v1 config", |
|
Since this is logically generic, moving the group makes sense. It does raise some questions about introducing a v2, but sparse versions should work. /lgtm |
|
/retest |
|
the pull-kubernetes-node-e2e-containerd failure is known, not a flake, non-blocking, and being worked on - #85040 |
|
/retest Review the full test history for this PR. Silence the bot with an |
What type of PR is this?
/kind cleanup
What this PR does / why we need it:
resourcequota.admission.k8s.io/v1beta1, kind=Configurationtoapiserver.config.k8s.io/v1, kind=ResourceQuotaConfigurationapiserver.config.k8s.iogroup for generic API server configuration was determined after the configuration type was introducedConfigurationsuffix is used consistently for top-level configuration typesDoes this PR introduce a user-facing change?:
/cc @derekwaynecarr @deads2k @ahg-g @ravisantoshgudimetla