Skip to content

Conversation

@stmcginnis
Copy link

This proposes adding a new configuration setting to be able to block reboots on nodes that have matching labels applied, similar to the pod selector and annotation locking.

The user can specify one or more --block-node-label parameters, using the same kubectl label selector format to match and block on whether a label is present (e.g. my.custom.label) or if the label is set to a specific value (e.g. my.custom.label:block-reboots).

This adds a new configuration setting to be able to block reboots on
nodes that have matching labels applied, similar to the pod selector and
annotation locking.

The user can specify one or more `--block-node-label` parameters, using
the same kubectl label selector format to match and block on whether a
label is present (e.g. `my.custom.label`) or if the label is set to a
specific value (e.g. `my.custom.label:block-reboots`).

Signed-off-by: Sean McGinnis <sean.mcginnis@gmail.com>
@evrardjp
Copy link
Collaborator

evrardjp commented Oct 5, 2025

Would you mind writing about your use case? I would like to have it on the record. This is for history's sake :)

I think it's also worth doing an e2e test, this way v2 will not break this workflow.

@github-actions
Copy link

github-actions bot commented Dec 6, 2025

This PR was automatically considered stale due to lack of activity. Please refresh it and/or join our slack channels to highlight it, before it automatically closes (in 7 days).

@evrardjp evrardjp added enhancement This was triaged as an enhancement keep This won't be closed by the stale bot. FEATURE-v2 This is a feature improvement that needs to be taken into consideration for v2 and removed no-pr-activity labels Dec 8, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

enhancement This was triaged as an enhancement FEATURE-v2 This is a feature improvement that needs to be taken into consideration for v2 keep This won't be closed by the stale bot.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants