Skip to content
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

feat(helm): Introduce priorityClassName system-node-critical #220

Merged
merged 2 commits into from
Jan 10, 2024

Conversation

ffuerste
Copy link
Contributor

@ffuerste ffuerste commented Jan 6, 2024

What does this PR do?

Introducing in the helm charts of all NRI plugins an optional boolean field for setting priorityClassName: system-node-critical.

As suggest here the priorityClassName is introduced as an optional helm flag analog to patchRuntimeConfig. However, in this way the feature can only be enabled with no option to define a custom priorityClassName.

Related issues

Resolves #194

@ffuerste ffuerste changed the title feat(helm): Introduced priorityClassName system-node-critical feat(helm): Introduce priorityClassName system-node-critical Jan 6, 2024
…as an optional boolean value

Signed-off-by: Florian Fürstenberg <[email protected]>
Copy link
Collaborator

@marquiz marquiz left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the patch @ffuerste. This totally makes sense.

I'm just wondering should be the desired default be true, for at least some of the plugins 🧐 If a resource policy plugin (like balloons or topology-aware) is deployed I think it is kinda critical and should not be evicted (thus default to true). WDYT? @klihub @fmuyassarov @askervin @kad

Copy link
Collaborator

@askervin askervin left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think this is a very nice improvement.

I'm fine both merging this PR as it is, or with some/all existing plugins set as system-node-critical by default.

Maybe I'd even prefer taking this PR is as it is, as it only enables configuring the priorityClassName but does not change the default behavior. And then have a separate commit that changes the default behavior for chosen plugins.

@fmuyassarov
Copy link
Collaborator

Thanks for the patch @ffuerste. This totally makes sense.

I'm just wondering should be the desired default be true, for at least some of the plugins 🧐 If a resource policy plugin (like balloons or topology-aware) is deployed I think it is kinda critical and should not be evicted (thus default to true). WDYT? @klihub @fmuyassarov @askervin @kad

I don't have a strong opinion about that to be frank. I'm fine with the current state as well.

@kad
Copy link
Collaborator

kad commented Jan 8, 2024

I think it makes sense.

Copy link
Collaborator

@klihub klihub left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM.

@klihub
Copy link
Collaborator

klihub commented Jan 8, 2024

Thanks for the patch @ffuerste. This totally makes sense.

I'm just wondering should be the desired default be true, for at least some of the plugins 🧐 If a resource policy plugin (like balloons or topology-aware) is deployed I think it is kinda critical and should not be evicted (thus default to true). WDYT? @klihub @fmuyassarov @askervin @kad

I'm fine with the default either way for the current plugins.

Copy link
Collaborator

@marquiz marquiz left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hold until comments are resolved

…ass for node-critical pods

Signed-off-by: Florian Fürstenberg <[email protected]>
Copy link
Collaborator

@marquiz marquiz left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks @ffuerste. LGTM on my part

@klihub klihub merged commit fcef94b into containers:main Jan 10, 2024
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Question: Adding Kubernetes priority class to NRI plugin deployment manifests
6 participants