Repository navigation
Replies: 1 comment 2 replies
|
Are you doing a deployment directly via the deployment.yaml? When you use OLM based deployment only single / own namespace are supported and role bindings should be used. |
2 replies
|
Typically yes. Deploying to a single namespace is desired, but the operator itself requires cluster wide permissions. |
|
I had forgotten about the cluster role for getting the Ingress config - that allows for us to generate a hostname on openshift. If that clusterrole were omitted it wouldn't cause a problem for plain kubernetes. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
I'd like to use Keycloak Operator to deploy Keycloak in a Kubernetes cluster, but that cluster has strict multi-tenant requirements. The security policies on the cluster don’t allow me to use any cluster-level permissions (like ClusterRoles or ClusterRoleBindings), which is currently preventing me from deploying the Keycloak Operator due to its cluster-wide RBAC resources.
Is it possible to deploy keycloak operator without these permissions (eg using Role and RoleBinding instead), or would it be difficult to modify the operator to enable more tightly scoped deploys?
All reactions