-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
[1.33] promote KEP-3902 to stable #4392
base: master
Are you sure you want to change the base?
Conversation
carlory
commented
Jan 8, 2024
- One-line PR description: promote KEP-3902 to stable
- Issue link: Decouple TaintManager from NodeLifecycleController #3902
- Other comments:
/cc @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.
You'll need the following to push this forward:
- Get a sig-scheduling lead opt-in this feature into 1.30, last time I see it was Aldo, so you should ping him about that
- Update the README.md with appopriate changes, from a quick skim you're missing:
- release checklist updated
- update tests with links to testgrid, based on tests added in beta
- describe feedback/bugs you noticed during beta
- update implementation history
thanks for your review. I'll fill it later. |
/hold |
/hold cancel 1.30 is released. |
/cc @Huang-Wei @alculquicondor |
690a0e5
to
06daa76
Compare
@@ -140,24 +140,29 @@ The creation and startup of the default taint-manager is performed by `kube-cont | |||
Kubernetes already has a good coverage of node `No-Execute` eviction. We will add tests only for the changed code. | |||
|
|||
##### Unit tests | |||
- `pkg/controller/taintmanager`: 2023-06-03 - 0% (to add) | |||
- `pkg/controller/tainteviction`: 2024-09-18 - 81.8% | |||
- Enable and disable the new `TaintEvictionController` | |||
- The new `TaintEvictionController` acts on node taints properly | |||
- `pkg/controller/apis/config/v1alpha1`: 2023-06-03 - 0% | |||
- Test new configuration |
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.
kubernetes/kubernetes#119208 did not introduce any new configuration. I want to check if we want to implement this item before promoting it to GA.
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 still unresolved, either new configuration was added or not, in either case we need to update the doc to reflect that.
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 removed it but still need some feedback from the original author of this KEP
/hold
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.
/cc @yuanchen8911 @atosatto
Could you have a look when you have time?
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.
A few minor prr comments, you're still missing approval from sig-scheduling.
@@ -140,24 +140,29 @@ The creation and startup of the default taint-manager is performed by `kube-cont | |||
Kubernetes already has a good coverage of node `No-Execute` eviction. We will add tests only for the changed code. | |||
|
|||
##### Unit tests | |||
- `pkg/controller/taintmanager`: 2023-06-03 - 0% (to add) | |||
- `pkg/controller/tainteviction`: 2024-09-18 - 81.8% | |||
- Enable and disable the new `TaintEvictionController` | |||
- The new `TaintEvictionController` acts on node taints properly | |||
- `pkg/controller/apis/config/v1alpha1`: 2023-06-03 - 0% | |||
- Test new configuration |
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 still unresolved, either new configuration was added or not, in either case we need to update the doc to reflect that.
@@ -173,14 +178,18 @@ Since there are no new API changes, we can skip Alpha and go to Beta directly. | |||
|
|||
#### GA |
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 believe @ravisantoshgudimetla has some use cases for this particular feature. Feel free to sync with him about that.
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.
/approve
the PRR portion
The Kubernetes project currently lacks enough contributors to adequately respond to all PRs. This bot triages PRs according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
/remove-lifecycle stale |
Co-authored-by: Aldo Culquicondor <[email protected]> Signed-off-by: carlory <[email protected]>
/cc @wojtek-t @yuanchen8911 @atosatto |
Now that Wojtek is taking this over |
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: alculquicondor, carlory, yuanchen8911 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 |