-
Notifications
You must be signed in to change notification settings - Fork 114
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
Validate .Spec.DisableDrain #464
Validate .Spec.DisableDrain #464
Conversation
Thanks for your PR,
To skip the vendors CIs use one of:
|
3715423
to
9096080
Compare
Thanks for your PR,
To skip the vendors CIs use one of:
|
9096080
to
a40aa44
Compare
Thanks for your PR,
To skip the vendors CIs use one of:
|
Pull Request Test Coverage Report for Build 5452582694
💛 - Coveralls |
a40aa44
to
c262772
Compare
Thanks for your PR,
To skip the vendors CIs use one of:
|
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 will technically not solve the issue, but narrow down the when it might happen.
minor nit otherwise lgtm.
Early exit from the function to make the validation logic more evident and allow further improvements. Signed-off-by: Andrea Panattoni <[email protected]>
Disable the drain while a node is updating its configuration prevents the config-daemon to uncordon the node, leading to a node that needs to be manually uncordoned. Signed-off-by: Andrea Panattoni <[email protected]>
c262772
to
91ea65f
Compare
Thanks for your PR,
To skip the vendors CIs use one of:
|
This PR introduces a webhook validation for the
SriovOperatorConfig
to avoid disabling the drain whilethe config-daemon is updating a node. Disabling the drain at this stage would prevent the operator to uncordon a node at the end of the update operation, keeping nodes un-schedulable until manual intervention.
Introduce a small refactor of
validateSriovOperatorConfig(...)
this PR needs
cc @mlguerrero12