-
Notifications
You must be signed in to change notification settings - Fork 4
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
Add spec.type
to Node Disruption API
#64
Comments
FatmaBouzghaia
pushed a commit
to FatmaBouzghaia/node-disruption-controller
that referenced
this issue
Jun 24, 2024
Signed-off-by: f.bouzghaia <[email protected]>
FatmaBouzghaia
pushed a commit
to FatmaBouzghaia/node-disruption-controller
that referenced
this issue
Jun 25, 2024
Signed-off-by: f.bouzghaia <[email protected]>
FatmaBouzghaia
pushed a commit
to FatmaBouzghaia/node-disruption-controller
that referenced
this issue
Jun 25, 2024
Signed-off-by: f.bouzghaia <[email protected]>
FatmaBouzghaia
pushed a commit
to FatmaBouzghaia/node-disruption-controller
that referenced
this issue
Jun 28, 2024
Signed-off-by: f.bouzghaia <[email protected]>
FatmaBouzghaia
pushed a commit
to FatmaBouzghaia/node-disruption-controller
that referenced
this issue
Jun 28, 2024
Signed-off-by: f.bouzghaia <[email protected]>
FatmaBouzghaia
pushed a commit
to FatmaBouzghaia/node-disruption-controller
that referenced
this issue
Jun 28, 2024
Signed-off-by: f.bouzghaia <[email protected]>
geobeau
pushed a commit
that referenced
this issue
Jun 28, 2024
Implement #64 Signed-off-by: f.bouzghaia <[email protected]> Co-authored-by: f.bouzghaia <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Spec type will contains the type of the disruption. This type is a set of arbitrary strings such as: "decommission", "reboot", etc.
There should be a way to specify an allow list of types (so we can control which types are supported). It will have the following requirements:
This type should also be used to segregate metrics (both budget and node disruption) to allow better observability.
The text was updated successfully, but these errors were encountered: