Support global vars, volumes and volumeMounts for workspace statefulsets within helm chart

[drduker]

Hello!

Support global vars, volumes and volumeMounts for workspace statefulsets from the operator being supported in the helm chart templates.

This is really an ask that should require two changes:

1. Add helm templating to create a place for global values or a flag to have workspace pods inherit envs,volumes and volumeMounts from the operator config.
2. Make the operator deploy statefulsets using additional global configs in addition to what comes from the workspaceTemplate with the stack configs.

• Vote on this issue by adding a 👍 reaction
• If you want to implement this feature, comment to let us know (we'll work with you on design, scheduling, etc.)

Issue details

Affected area/feature

[EronWright]

I take this as a feature request to provide for global customization of the Workspace. I suppose the operator could have a cluster-scoped and/or namespace-scoped configuration object, providing a default workspace template (and would be merged with the stack's own template). The Helm chart could then produce this object.

A possible workaround would be to use a mutating webhook, to apply some defaults into the Stack object or directly into the Workspace object.

@drduker to help make the case for this feature, could you share some specific use cases that you have in mind?

[drduker]

Use case is an offline deployment where you have local libraries that require netrc variables set. This vars need to go onto the workspace pods. Could use kyvero yes. I’m setting the values per stack in the workspace template values now. But it’s redundant and was not quick to find the usage for that. Had to look up spec and play around with that.

[EronWright]

See also: #797