James Strachan

which version of kubernetes-api, kubernetes-client, kubernetes-model are you using? e.g. try running `mvn dependency:version` and posting the output here?

@eivantsov many thanks! I guess the `${CLIENT_ID}` is the ID of the main fabric8 client right? (which is currently `fabric8-online-platform` in keycloak? Here's a PR that includes the above env...

ah, the `che DeploymentConfig` for minishift in `developer-che` was set to 0 replicas. I manually scaled it up for now. Then if I go to https://che-developer-che.192.168.64.82.nip.io/ I get a 403....

in the che pod in developer-che I get this when I try access https://che-developer-che.192.168.64.82.nip.io/ directly - I guess its due to my browser not being authenticated? ``` NFO: KeycloakSettings =...

ah ;) wrong keycloak URL there ;)

the redirect URL in KeyCloak should that be for che-starter or for the che pod in the developer-che namespace?

ah ok, so we're gonna have to get fabric8-tenant to register a new KeyCloak redirectURI for each new tenant (since each tenant gets its own che pod)

KC doesn't support wildcards in the host name part of the URL; only in the path - we faced a similar issue with Jenkins on Kubernetes. Each Che pod has...

so I tried doing the above manually on my minishift; so these env vars are inside the `che` pod in `developer-che` ``` CHE_KEYCLOAK_AUTH__SERVER__URL=http://keycloak-fabric8.192.168.64.82.nip.io/auth CHE_KEYCLOAK_REALM=fabric8 CHE_KEYCLOAK_CLIENT__ID=fabric8-online-platform ``` then KeyCloak has the...

ah - the "Access Type" of the `fabric8-online-platform` client in KeyCloak has to be setup as `public` right? The KeyCloak admin UI won't let me set that :) will try...