Support custom service account for DevWorkspaces #20535
Labels
area/che-server
area/devworkspace-operator
kind/enhancement
A feature request - must adhere to the feature request template.
lifecycle/stale
Denotes an issue or PR has remained open with no activity and has become stale.
severity/P2
Has a minor but important impact to the usage or development of the system.
Is your enhancement related to a problem? Please describe
Che server can be configured to use a custom service account for workspaces. It can also be configured with custom set of cluster roles that it should bind to the workspace service account. This enables the users to give extra permissions to the workspace pods, should they need it.
We should add this capability to DevWorkspaces, too.
Describe the solution you'd like
IMHO it would work better in the devworkspace-operator "world" if we supported using a pre-existing labeled service account from the user's namespace for workspaces within (and auto-create the service account if no such SA exists).
This would gives us (or the cluster administrator) the ability to prepare the namespace for correct function before any DevWorkspace is deployed there.
From Che point of view we could use the existing configuration for the custom service account and custom (cluster)roles to prepare such service account in the user's namespace. This should be read from the
CHE_INFRA_KUBERNETES_WORKSPACE__SA__CLUSTER__ROLES
fromcustomCheProperties
andcheWorkspaceClusterRole
properties inCheCluster
v1 and should have some dedicated field(s) inCheCluster
v2alpha1, too.Describe alternatives you've considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: