`oauth-proxy` container in `che-gateway` pod throws error while setting up `eclipse-che` on k8s cluster
See original GitHub issueSummary
i have configured a k8s cluster in my virtual machine and i installed eclipse-che
using below command. the installation completed, but i have explained the issue below
chectl server:deploy --che-operator-cr-patch-yaml=/home/ubuntu/kubeapps/che-operator-cr-patch.yaml --platform=k8s --installer=operator --debug --k8spoderrorrechecktimeout=480000 --domain=eclipseche.mangotree.click --k8spodreadytimeout=480000
i was able to follow this documentation and integrate dex
with an example-app successfully. Now i have to integrate dex
and eclipse-che
.
below screenshot shows the output after successfully installing eclipse-che in k8s cluster but without integrating eclipse-che
with dex
.
But what steps should i follow to inregrate eclipse-che
and dex
?
(not real url)sample url is https://eclipseche.example.click:31931/ , https://eclipseche.example.click:31931/dashboard
i investigated the error and found che-gateway-766fdb7b54-pb8bz
pod in errored state. i investigated the state of the containers with-in the pod, oauth-proxy
container in che-gateway-766fdb7b54-pb8bz
pod is in errored state.
i checked the oauth-proxy
container logs in che-gateway-766fdb7b54-pb8bz
pod , it shows below error message. where should i update the information mentioned in the error message ?
Please help me on what should i do to fix this error?
Relevant information
No response
Issue Analytics
- State:
- Created a year ago
- Comments:13 (6 by maintainers)
Top GitHub Comments
oAuthClientName
andoAuthSecret
isid
andsecret
from Dex configuration https://github.com/dexidp/dex/blob/master/examples/config-dev.yaml#L110.Che will always talk to Dex here. If you want to login with GitHub, you have to configure Dex to connect to it https://dexidp.io/docs/connectors/github/
It looks like this: Che --(OIDC)–> Dex ----> Identity Provider (GitHub, Gitlab, Google, …)
Kubernetes must be using same Dex for authentication and by that we’re able to use Kubernetes RBAC to control permissions for users. It will also allow us to have various Identity providers.
chectl
command looks rightTry to clean up checluster CR manually
oc patch checluster/eclipse-che --patch '{"metadata": {"finalizers": null}}' --type=merge -n eclipse-che
Namespace should be deleted automatically.