-
Notifications
You must be signed in to change notification settings - Fork 40.1k
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
Remove generally available feature gate MinDomainsInPodTopologySpread #126863
Remove generally available feature gate MinDomainsInPodTopologySpread #126863
Conversation
This issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the The 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-sigs/prow repository. |
/sig scheduling |
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.
/lgtm
/approve
LGTM label has been added. Git tree hash: 874c8dccb1c75e2564efd14adb0ba9d72490cdbb
|
/assign @aojea |
624f739
to
8919e0c
Compare
8919e0c
to
c2a3009
Compare
/test pull-kubernetes-integration |
/lgtm |
LGTM label has been added. Git tree hash: ea0cd8424d1751fd0988ae85b6f82ea910ac63c8
|
/cc @aojea |
It looks correct @logicalhan can you PTAL to check the removal of feature gates with the versioning thing is correct? /assign @thockin |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: aojea, carlory, sanposhiho 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 cleanup
What this PR does / why we need it:
GA: v1.30
A follow-up of #123481
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?
Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.: