Skip to content
This repository has been archived by the owner on Mar 17, 2021. It is now read-only.

verifying that chectl can deploy multiuser Che without cluster admin privileges #1609

Closed
ibuziuk opened this issue Sep 10, 2019 · 5 comments
Closed

Comments

@ibuziuk
Copy link
Member

ibuziuk commented Sep 10, 2019

@l0rd I remember we discussed this issue during prioritization, but as I understand currently cluster-admin is a requirement according to the error message:

[ibuziuk@fedora ~]$ chectl server:start --platform=minishift --multiuser
✈️ Minishift preflight checklist
✔ Verify if oc is installed...done.
✔ Verify if minishift is installed...done.
✔ Verify if minishift is running...done.
❯ 🏃‍ Running the Che Operator
✔ Copying operator resources...done.
✔ Create Namespace (che)...done.
✔ Create ServiceAccount che-operator in namespace che...done.
✖ Create Role che-operator in namespace che
→ ERROR: It looks like you don't have enough privileges. You need to grant

Create ClusterRole che-operator
Create RoleBinding che-operator in namespace che
Create ClusterRoleBinding che-operator
Create CRD checlusters.org.eclipse.che
Waiting 5 seconds for the new Kubernetes resources to get flushed
Create deployment che-operator in namespace che
Create Che Cluster eclipse-che in namespace che
› Error: ERROR: It looks like you don't have enough privileges. You need to
› grant more privileges to current user or use a different user. If you are
› using minishift you can "oc login -u system:admin"

@ibuziuk
Copy link
Member Author

ibuziuk commented Sep 10, 2019

@l0rd could you please clarify the scope of this issue?

@ibuziuk ibuziuk added this to the Sprint #172 (Che OSIO) milestone Sep 10, 2019
@l0rd
Copy link
Contributor

l0rd commented Sep 11, 2019

@ibuziuk what I mean is that admin rights should not be required (except if the user wants to configure Keycloak to use OpenShift OAuth). Today for some reason we create a che-operator ClusterRole. Why do we need that? Can we avoid it?

@ibuziuk
Copy link
Member Author

ibuziuk commented Sep 25, 2019

Closing in favour of upstream - eclipse-che/che#14662

@ibuziuk ibuziuk closed this as completed Sep 25, 2019
@hari1992-web
Copy link

Readiness probe failed: HTTP probe failed with statuscode: 500
Back-off restarting failed container

@hari1992-web
Copy link

Does any way fix it ??
thanks in advance

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants