-
Notifications
You must be signed in to change notification settings - Fork 1.6k
KEP-3243: Update milestone v1.33 to v1.34 and add the new feature gate to control the design change of TopologySpreadConstraint's matchLabelKeys #5205
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
KEP-3243: Update milestone v1.33 to v1.34 and add the new feature gate to control the design change of TopologySpreadConstraint's matchLabelKeys #5205
Conversation
/cc @sanposhiho |
1a3dbd2
to
4e8004a
Compare
keps/sig-scheduling/3243-respect-pod-topology-spread-after-rolling-upgrades/README.md
Show resolved
Hide resolved
4e8004a
to
39ebbdc
Compare
I've merged #5214 into this change. |
keps/sig-scheduling/3243-respect-pod-topology-spread-after-rolling-upgrades/README.md
Outdated
Show resolved
Hide resolved
keps/sig-scheduling/3243-respect-pod-topology-spread-after-rolling-upgrades/README.md
Outdated
Show resolved
Hide resolved
keps/sig-scheduling/3243-respect-pod-topology-spread-after-rolling-upgrades/README.md
Outdated
Show resolved
Hide resolved
keps/sig-scheduling/3243-respect-pod-topology-spread-after-rolling-upgrades/README.md
Outdated
Show resolved
Hide resolved
b154ec0
to
8148d60
Compare
/cc @sanposhiho |
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 /hold |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: macsko, mochizuki875 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 |
@wojtek-t |
If this is going from beta -> stable than I think a PRR review is required. If you are staying in beta, I am not sure a PRR review is required. I did take a look on this. Can you update the following question? The issue merged so I think this could be updated. |
@kannon92 |
@kannon92 @sanposhiho @macsko |
@@ -897,8 +897,7 @@ Pick one more of these and delete the rest. | |||
Describe the metrics themselves and the reasons why they weren't added (e.g., cost, | |||
implementation difficulties, etc.). | |||
--> | |||
Yes. It's helpful if we have the metrics to see which plugins affect to scheduler's decisions in Filter/Score phase. | |||
There is the related issue: https://github.com/kubernetes/kubernetes/issues/110643 . It's very big and still on the way. | |||
No. |
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.
nit: to make it clear
Yes, [there were](https://github.com/kubernetes/kubernetes/issues/110643), and it's been implemented in xxx and yyy.
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.
OK, I've updated.
/lgtm Keep |
/lgtm from PRR perspective /hold cancel |
One-line PR description: Update KEP milestone v1.33 to v1.34 since the code change have not meet the v1.33 code freeze, and I've added the new feature gate for #129874 as discussed in kubernetes/kubernetes#129874 (comment).
Issue link: #3243
Other comments: