-
Notifications
You must be signed in to change notification settings - Fork 1.6k
KEP-3094: Graduate NodeInclusionPolicy to Beta in v1.26 #3539
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-3094: Graduate NodeInclusionPolicy to Beta in v1.26 #3539
Conversation
Signed-off-by: kerthcet <[email protected]>
keps/sig-scheduling/3094-pod-topology-spread-considering-taints/README.md
Show resolved
Hide resolved
Signed-off-by: kerthcet <[email protected]>
|
Still missing the |
Signed-off-by: kerthcet <[email protected]>
|
Update the stage to beta. |
keps/sig-scheduling/3094-pod-topology-spread-considering-taints/README.md
Outdated
Show resolved
Hide resolved
keps/sig-scheduling/3094-pod-topology-spread-considering-taints/README.md
Outdated
Show resolved
Hide resolved
keps/sig-scheduling/3094-pod-topology-spread-considering-taints/README.md
Show resolved
Hide resolved
keps/sig-scheduling/3094-pod-topology-spread-considering-taints/README.md
Outdated
Show resolved
Hide resolved
| ###### What steps should be taken if SLOs are not being met to determine the problem? | ||
| N/A | ||
| Check the metrics to see whether it was caused by this feature, if so, disable the feature gate. |
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.
How do we determine that this feature is the problem?
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.
To some extent, we can observe this via the Metric plugin_execution_duration_seconds{plugin="PodTopologySpread"}, if we see obviously execution time latency when enabling the feature-gate, then we may have some problems in PodTopologySpread plugin.
Signed-off-by: kerthcet <[email protected]>
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 from sig-scheduling
| ``` | ||
| 6. Both pods will be scheduled successfully. | ||
| - Details: We can only observe the behaviors based on pod scheduling results. | ||
| We can follow the steps described at [Upgrade / Downgrade Strategy](#upgrade--downgrade-strategy). |
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.
how is this related?
I would just remove this line
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.
In case someone want to know the details about how to reproduce this. I'll remove this.
Signed-off-by: kerthcet <[email protected]>
|
/approve |
|
cc @wojtek-t for PRR. |
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.
Couple small nits - other than that LGTM.
keps/sig-scheduling/3094-pod-topology-spread-considering-taints/README.md
Show resolved
Hide resolved
| are missing a bunch of machinery and tooling and can't do that now. | ||
| --> | ||
|
|
||
| Not yet, but it will be tested manually prior to upgrade following below steps: |
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 scenario LGTM - please update the PRR once you run it (fine to do this after feature freeze, but please do that before graduating the feature to beta in k/k).
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.
Then let's merge this PR first for I may leave several days.. And I'll update this section after.
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.
SG
Signed-off-by: kerthcet <[email protected]>
|
cc @wojtek-t for another round of review. Thanks. |
|
|
||
| ###### Are there any tests for feature enablement/disablement? | ||
| No, appropriate unit tests will be added for Alpha. | ||
| Yes, both unit tests and integration tests are added. |
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.
Can you please link them here?
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.
Updated @wojtek-t
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.
Those aren't typical enablement/disablement tests - those test the feature when it is enabled/disabled.
The enablement/disablement tests change whether the feature is enabled/disabled in the middle of the test.
On the scheduler side this seems to be good enough, because in scheduler this is basically "in-memory" feature.
So maybe please add something like:
"In the scheduler, this is in-memory feature, so only tests checking both feature being enabled and disabled were added".
However, this KEP is also introducing an API change, so a test similar to this one would be useful on the registry side:
https://github.com/kubernetes/kubernetes/pull/97058/files#diff-7826f7adbc1996a05ab52e3f5f02429e94b68ce6bce0dc534d1be636154fded3R246-R282
Would you be able to add something like that?
I don't want to block this PR, so if you could add here that a strategy test will be added and add that to beta graduation criteria, I would be fine.
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 add the test here kubernetes/kubernetes#112805, PTAL @wojtek-t
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.
@kerthcet - I don't want to block Beta on it - can you please add here that such test will be added (and add that to beta graduation criteria) and I will approve the PRR then?
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.
Updated the enablement tests again. PTAL.
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.
@kerthcet the KEP freeze is tomorrow. Just update this PR to say that the tests will be added (linking to the PR is fine too).
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.
Updated.
Signed-off-by: kerthcet <[email protected]>
Signed-off-by: kerthcet <[email protected]>
|
/lgtm |
|
/lgtm /hold cancel |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: alculquicondor, kerthcet, wojtek-t 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 |
) * Graduate NodeInclusionPolicy to Beta Signed-off-by: kerthcet <[email protected]> * update PRR files Signed-off-by: kerthcet <[email protected]> * update the stage to beta Signed-off-by: kerthcet <[email protected]> * address comments Signed-off-by: kerthcet <[email protected]> * address comments Signed-off-by: kerthcet <[email protected]> * Make sure feature gate enable/disable tested Signed-off-by: kerthcet <[email protected]> * add feature gate enabled/disabled testcases Signed-off-by: kerthcet <[email protected]> * Add descriptions about feature enable/disable tests Signed-off-by: kerthcet <[email protected]> Signed-off-by: kerthcet <[email protected]>
Signed-off-by: kerthcet [email protected]