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
Scheduler: graduate DefaultPodTopologySpread to GA #107421
Scheduler: graduate DefaultPodTopologySpread to GA #107421
Conversation
@gavinfish: 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/test-infra repository. |
27c5535
to
f651af9
Compare
/assign @alculquicondor |
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. |
@@ -114,90 +113,6 @@ func TestApplyFeatureGates(t *testing.T) { | |||
}, | |||
}, | |||
}, | |||
{ | |||
name: "DefaultPodTopologySpread disabled", |
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.
keep this test but change to another plugin, like JobTrackingWithFinalizers
?
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.
That's not a plugin. That's a feature for the job controller.
But there should be a test for VolumeCapacityPriority
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.
I can create a separate PR to add more test for VolumeCapacityPriority
.
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.
sorry for wrong words, but shouldn't we change to a beta feature, and verify whether disable this feature-gate works? VolumeCapacityPriority
is alpha now and disabled by default.
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.
unit tests are independent of whether the feature is alpha or beta. The test itself sets the value of the gate, regardless of the graduation status.
@@ -904,7 +904,7 @@ var defaultKubernetesFeatureGates = map[featuregate.Feature]featuregate.FeatureS | |||
HugePageStorageMediumSize: {Default: true, PreRelease: featuregate.GA, LockToDefault: true}, // remove in 1.24 | |||
DownwardAPIHugePages: {Default: true, PreRelease: featuregate.Beta}, // on by default in 1.22 | |||
AnyVolumeDataSource: {Default: false, PreRelease: featuregate.Alpha}, | |||
DefaultPodTopologySpread: {Default: true, PreRelease: featuregate.Beta}, |
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.
Since PodTopologySpread graduated to GA, should we remove SelectorSpread then? @alculquicondor
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.
We can't, because it's a supported plugin in v1beta3. We can potentially remove it once we release a v1. Maybe we will do that in 1.25.
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.
The feature gate itself should be removed two releases after graduation. That's 1.26.
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.
Or we can add some related comments. Forget it if not necessary.
/hold |
@alculquicondor PTAL Left work for GA is updating documentation, right? |
/hold cancel |
@@ -221,7 +220,7 @@ leaderElection: | |||
name: "default config with an alpha feature enabled and an beta feature disabled", | |||
flags: []string{ | |||
"--kubeconfig", configKubeconfig, | |||
"--feature-gates=VolumeCapacityPriority=true,DefaultPodTopologySpread=false", | |||
"--feature-gates=VolumeCapacityPriority=true,JobMutableNodeSchedulingDirectives=false", |
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 not a feature that affects kube-scheduler. Just get rid of the "and a beta feature disabled" part of the test. In this test, we should only care about features that affect the config.
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.
done
@@ -904,7 +904,7 @@ var defaultKubernetesFeatureGates = map[featuregate.Feature]featuregate.FeatureS | |||
HugePageStorageMediumSize: {Default: true, PreRelease: featuregate.GA, LockToDefault: true}, // remove in 1.24 | |||
DownwardAPIHugePages: {Default: true, PreRelease: featuregate.Beta}, // on by default in 1.22 | |||
AnyVolumeDataSource: {Default: false, PreRelease: featuregate.Alpha}, | |||
DefaultPodTopologySpread: {Default: true, PreRelease: featuregate.Beta}, |
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.
The feature gate itself should be removed two releases after graduation. That's 1.26.
f651af9
to
451c03f
Compare
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.
Update the comments for:
// Defaults to "List" if feature gate DefaultPodTopologySpread is disabled // Defaults to "List" if feature gate DefaultPodTopologySpread is disabled // Defaults to "List" if feature gate DefaultPodTopologySpread is disabled
451c03f
to
fb96a68
Compare
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
/label api-review
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: alculquicondor, gavinfish The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/assign @lavalamp |
@gavinfish: PR needs rebase. 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. |
ping @gavinfish please rebase this pr. |
Is it possible by help rebasing this pr, I'll cherry pick @gavinfish 's commit as he does the most of the work. @alculquicondor |
Please do, it's been several days since @gavinfish last answered. |
Create #108278 and cherry pick the commit already. Feel free to close this one. |
/close |
@alculquicondor: Closed this PR. 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. |
What type of PR is this?
/kind feature
What this PR does / why we need it:
graduate DefaultPodTopologySpread to GA
Which issue(s) this PR fixes:
REF: kubernetes/enhancements#1258
Special notes for your reviewer:
Does this PR introduce a user-facing change?
Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.: