Add supported disruption types field to disruption budgets#77
Merged
hamza-boudouche merged 1 commit intocriteo:mainfrom Feb 13, 2026
Merged
Add supported disruption types field to disruption budgets#77hamza-boudouche merged 1 commit intocriteo:mainfrom
hamza-boudouche merged 1 commit intocriteo:mainfrom
Conversation
The Application and Node Disruption Budget CRDs now have a new field `.spec.supportedDisruptionTypes` that indicated whether the budget should be considered when reconciling a NodeDisruption of a certain type. The idea behind this is that for certain special types of disruptions, some budgets might not be impacted by them, and so the budget chooses to not support that type of disruption. The NodeDisruption reconciler will then only consider budgets supporting the type of the NodeDisruption it is currently reconciling. The new field `.spec.supportedDisruptionTypes` can have a default value that is set via a new cli flag `--default-node-disruption-types`. For existing installations, set the value of `--default-node-disruption-types` to the same value previously used for `--node-disruption-types`. The function of `--node-disruption-types` remains unchanged.
damsallem
approved these changes
Feb 13, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The Application and Node Disruption Budget CRDs now have a new field
.spec.supportedDisruptionTypesthat indicates whether the budget should be considered when reconciling a NodeDisruption of a certain type.The idea behind this is that for certain special types of disruptions, some budgets might not be impacted by them, and so the budget chooses to not support that type of disruption. The NodeDisruption reconciler will then only consider budgets supporting the type of the NodeDisruption it is currently reconciling.
The new field
.spec.supportedDisruptionTypescan have a default value that is set via a new cli flag--default-node-disruption-types. For existing installations, set the value of--default-node-disruption-typesto the same value previously used for--node-disruption-types. The function of--node-disruption-typesremains unchanged.