flux2

Commit Graph

Author	SHA1	Message	Date
Max Jonas Werner	a21fd5a0e3	feat: create view/edit ClusterRoles upon install This way users can make use of these roles by having them aggregated into the 'view', 'admin' and 'edit' ClusterRoles present on Kubernetes clusters by default. Without these roles you would have to bind subjects in a confined Namespace to the `cluster-admin` ClusterRole which lets them create cluster-scoped resources. To really confine subjects to a single Namespace you would rather want to bind them to the `admin` or `edit` ClusterRole so that they cannot create cluster-scoped resources. This is where these new ClusterRoles created in this commit come into play, letting subjects bound to one of these two ClusterRoles created Flux CRDs such as HelmRelease or Kustomization. Signed-off-by: Max Jonas Werner <mail@makk.es>	4 years ago

Author

SHA1

Message

Date

Max Jonas Werner

a21fd5a0e3

feat: create view/edit ClusterRoles upon install

This way users can make use of these roles by having them
aggregated into the 'view', 'admin' and 'edit' ClusterRoles
present on Kubernetes clusters by default.

Without these roles you would have to bind subjects in a confined
Namespace to the `cluster-admin` ClusterRole which lets them create
cluster-scoped resources. To really confine subjects to a single
Namespace you would rather want to bind them to the `admin` or `edit`
ClusterRole so that they cannot create cluster-scoped resources. This
is where these new ClusterRoles created in this commit come into play,
letting subjects bound to one of these two ClusterRoles created Flux
CRDs such as HelmRelease or Kustomization.

Signed-off-by: Max Jonas Werner <mail@makk.es>

1 Commits (a21fd5a0e32413ab3098ae7825730a7f871aee15)