Eclipse che 7.43.0 is always failing to deploy with k8s as platform

Summary

Hi, I’m trying to install eclipse-che 7.43.0 on kubernetes cluster. This is always failing with error that Kubernetes API Server needs to be configured with OIDC provider. This is the same even if I use --skip-oidc-provider-check otpion.

Error: API server is not configured with OIDC Identity Provider, see details https://kubernetes.io/docs/reference/access-authn-authz/authentication/#configuring-the-api-server. To bypass OIDC Provider check, use '--skip-oidc-provider-check' flag

I also configured --che-operator-cr-patch-yaml with external keycloak option with no different result.

Here is my command execution: chectl server:deploy --installer=operator --platform=k8s --multiuser --che-operator-cr-patch-yaml=poc_minimal_che_config.yaml -v=7.43.0 --chenamespace=poc

Error log: 8:57.860Z Cause: Error: API server is not configured with OIDC Identity Provider, see details https://kubernetes.io/docs/reference/access-authn-authz/authentication/#configuring-the-api-server. To bypass OIDC Provider check, use '--skip-oidc-provider-check' flag 2022-02-10T15:48:57.860Z at ~/.local/share/chectl/client/7.43.0/lib/commands/server/deploy.js:440:19 2022-02-10T15:48:57.860Z at Generator.next (<anonymous>) 2022-02-10T15:48:57.860Z at fulfilled (~/.local/share/chectl/client/7.43.0/node_modules/tslib/tslib.js:114:62) 2022-02-10T15:51:14.742Z Warning: Consider using the more reliable 'OLM' installer when deploying a stable release of Eclipse Che (--installer=olm). 2022-02-10T15:51:14.742Z at Object.warn (/root/.local/share/chectl/client/7.43.0/node_modules/@oclif/errors/lib/index.js:49:15) 2022-02-10T15:51:14.742Z at Deploy.warn (/root/.local/share/chectl/client/7.43.0/node_modules/@oclif/command/lib/command.js:57:16) 2022-02-10T15:51:14.742Z at OperatorTasks.<anonymous> (/root/.local/share/chectl/client/7.43.0/lib/tasks/installers/operator.js:151:25) 2022-02-10T15:51:14.742Z at Generator.next (<anonymous>) 2022-02-10T15:51:14.742Z at fulfilled (/root/.local/share/chectl/client/7.43.0/node_modules/tslib/tslib.js:114:62) 2022-02-10T15:51:14.742Z at runMicrotasks (<anonymous>) 2022-02-10T15:51:14.742Z at processTicksAndRejections (node:internal/process/task_queues:96:5) 2022-02-10T16:01:23.053Z Error: Command server:deploy failed. Error log: /root/.cache/chectl/error.log. 2022-02-10T16:01:23.053Z at newError (~/.local/share/chectl/client/7.43.0/lib/util.js:199:19) 2022-02-10T16:01:23.053Z at Object.wrapCommandError (~/.local/share/chectl/client/7.43.0/lib/util.js:195:12) 2022-02-10T16:01:23.053Z at Deploy.<anonymous> (~/.local/share/chectl/client/7.43.0/lib/commands/server/deploy.js:226:35) 2022-02-10T16:01:23.053Z at Generator.throw (<anonymous>) 2022-02-10T16:01:23.053Z at rejected (~/.local/share/chectl/client/7.43.0/node_modules/tslib/tslib.js:115:69) 2022-02-10T16:01:23.053Z at runMicrotasks (<anonymous>) 2022-02-10T16:01:23.053Z Cause: Error: Failed to start a pod, reason: Error, exitCode: 137

Relevant information

No response

[EnergieZ]

Same problem for me, don’t found any easy solution for K8S on docker desktop (windows), and will have the same problem when going to production with managed K8S on OVH.

Che need to have an embeded solution, or enough documentation to do it 😃

[aushetty]

@tolusha I have tried installing keycloak OIDC within the kubernetes cluster as part of OIDC requirement for chectl. However this seems to fail as well . Could you please provide your steps/documentation on how you were able to install it in your local machine