Description
When defining a LoginSet or NodeSet using any name other than slinky, required fields (sssdConf, login.image, initconf.image) must be specified explicitly or the chart fails to render with errors such as:
Error: execution error at (slurm/templates/loginset/loginset-secret.yaml:21:8): sssdConf is required
When using the name slinky with enabled: true, none of these fields need to be set — they are silently satisfied by the defaults already present in values.yaml under loginsets.slinky.
This poses a challenge when creating additional login sets:
- We have to specify all the previously-defaulted settings
- If the "slinky" defaults change in a subsequent chart version, there will be skew between slinky and other-named login / nodeSets.
- There may be skew between loginSets even if they render without error, due to optional defaults that are not present in the non-slinky loginSet.
Expected Behavior
Default settings should apply to all loginSets and nodeSets, regardless of name.
Description
When defining a LoginSet or NodeSet using any name other than slinky, required fields (sssdConf, login.image, initconf.image) must be specified explicitly or the chart fails to render with errors such as:
When using the name slinky with enabled: true, none of these fields need to be set — they are silently satisfied by the defaults already present in values.yaml under loginsets.slinky.
This poses a challenge when creating additional login sets:
Expected Behavior
Default settings should apply to all loginSets and nodeSets, regardless of name.