-
Notifications
You must be signed in to change notification settings - Fork 60
Add procMount to nodesets Helm template #2356
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
base: main
Are you sure you want to change the base?
Changes from 1 commit
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change | ||||
|---|---|---|---|---|---|---|
|
|
@@ -171,6 +171,9 @@ nodesets: | |||||
| # Optional, defaults to empty string | ||||||
| # e.g. `* soft nofile 1024` | ||||||
| limitsConfig: "" | ||||||
| # Proc mount type for the slurmd container | ||||||
| # Optional, valid values: "Default", "Unmasked" | ||||||
| # procMount: "" | ||||||
|
||||||
| # procMount: "" | |
| # procMount: "Default" |
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 adds
spec.slurmd.security.procMount, but the NodeSet CRD also supportsspec.munge.security.procMount(same enum). If the intent is full “procMount passthrough” for NodeSets, consider templating it for the munge container as well (and documenting it in values.yaml), otherwise it’s unclear why only slurmd is supported.