Dashboard not reachable after successfully deploying eclipse che on AKS cluster
See original GitHub issueDescribe the bug
The dashboard page is not reachable even after the successful installation of the che in AKS.
Che version
next (development version)
Steps to reproduce
chectl server:deploy --platform=k8s --installer=operator --che-operator-cr-patch-yaml=C:\Users\Act9\Desktop\che.yaml --skip-oidc-provider-check --domain=impaktapps.com --k8spodreadytimeout=600000
Expected behavior
A dashboard page should open up.
Runtime
other (please specify in additional context)
Screenshots
DNS Zone Entries :
Installation method
chectl/next
Environment
Azure
Eclipse Che Logs
PS C:\Users\Act9> chectl server:deploy --platform=k8s --installer=operator --che-operator-cr-patch-yaml=C:\Users\Act9\Desktop\che.yaml --skip-oidc-provider-check --domain=impaktapps.com --k8spodreadytimeout=600000
› Current Kubernetes context: 'eclipse-che-2'
v Verify Kubernetes API...[1.23]
v Kubernetes preflight checklist
v Verify if kubectl is installed...[OK]
v Verify domain is set...[OK]
v Create Namespace eclipse-che...[Created]
v Install Cert Manager v1.8.2
v Apply resources...[Created]
v Wait for Cert Manager pods ready...[OK]
v Start following Eclipse Che installation logs...[OK]
v Deploy Eclipse Che operator
v Install Dev Workspace operator
v Create Namespace devworkspace-controller...[Created]
v Create Dev Workspace operator resources...[Created]
v Wait for Dev Workspace operator ready...[OK]
v Create DevWorkspaceOperatorConfig devworkspace-operator-config...[Created]
v Create ServiceAccount che-operator...[Created]
v Create RBAC
v Create Role che-operator-leader-election...[Created]
v Create Role che-operator...[Created]
v Create RoleBinding che-operator-leader-election...[Created]
v Create RoleBinding che-operator...[Created]
v Create RoleBinding eclipse-che-che-operator...[Created]
v Create RoleBinding eclipse-che-che-operator...[Created]
v Wait for Cert Manager pods ready...[OK]
v Create Certificate che-operator-serving-cert...[Created]
v Create Issuer che-operator-selfsigned-issuer...[Created]
v Create Service che-operator-service...[Created]
v Create CRD checlusters.org.eclipse.che...[Created]
v Waiting...[OK]
v Create Deployment che-operator...[Created]
v Eclipse Che Operator pod bootstrap
v Scheduling...[OK]
v Downloading images...[OK]
v Starting...[OK]
v Create ValidatingWebhookConfiguration org.eclipse.che...[Created]
v Create MutatingWebhookConfiguration org.eclipse.che...[Created]
v Create CheCluster Custom Resource...[Created]
v Wait for Eclipse Che ready
v Postgres pod bootstrap
v Scheduling...[OK]
v Downloading images...[OK]
v Starting...[OK]
v Devfile Registry pod bootstrap
v Scheduling...[OK]
v Downloading images...[OK]
v Starting...[OK]
v Plugin Registry pod bootstrap
v Scheduling...[OK]
v Downloading images...[OK]
v Starting...[OK]
v Dashboard pod bootstrap
v Scheduling...[OK]
v Downloading images...[OK]
v Starting...[OK]
v Gateway pod bootstrap
v Scheduling...[OK]
v Downloading images...[OK]
v Starting...[OK]
v Eclipse Che Server pod bootstrap
v Scheduling...[OK]
v Downloading images...[OK]
v Starting...[OK]
v Wait Eclipse Che active...[OK]
v Eclipse Che status check...[OK]
v Retrieving Eclipse Che self-signed CA certificate...[OK: C:\Users\Act9\AppData\Local\Temp\cheCA.crt]
v Prepare post installation output...[OK]
v Show important messages
v Eclipse Che next has been successfully deployed.
v Documentation : https://www.eclipse.org/che/docs/
v -------------------------------------------------------------------------------
v Users Dashboard : https://impaktapps.com/dashboard/
v -------------------------------------------------------------------------------
v Plug-in Registry : https://impaktapps.com/plugin-registry/v3/
v Devfile Registry : https://impaktapps.com/devfile-registry/
v -------------------------------------------------------------------------------
Command server:deploy has completed successfully in 09:14.
Additional context
Runtime : AKS Kubernetes version : 1.23.12
che.yaml
spec:
networking:
auth:
identityProviderURL: https://sts.windows.net/c21d796f-015a-4b0f-9c5f-800f7f6237f9/v2.0/
identityToken: access_token
oAuthClientName: e189add7-57c5-4d0c-9073-34b5a60ffde0
oAuthSecret: ccc6a45f-0a35-4d14-9a1f-e1400a51b8dd
oAuthScope: openid email profile 6dae42f8-4368-4678-94ff-3960e28e3630/user.read
components:
cheServer:
extraProperties:
CHE_OIDC_AUTH__SERVER__URL: https://sts.windows.net/c21d796f-015a-4b0f-9c5f-800f7f6237f9/v2.0/
CHE_OIDC_EMAIL__CLAIM: unique_name
Issue Analytics
- State:
- Created 9 months ago
- Comments:28 (2 by maintainers)
Top Results From Across the Web
Dashboard on AKS not working (too many redirects) #20761
Deployment is successfull and plugin registry, devfile registry, keycloak are working and reachable. If I navigate to dashboard ...
Read more >Ecllipe Che Installation in Azure - Eclipse
Im trying to install eclipse che in Azure Cloud. ... the eclipse che deployment shall install the keycloak within the AKS cluster.
Read more >Install chectl management tool for eclipse che - Microsoft Learn
This chectl CLI utility needs to be installed after you connect to the azure subscription that is running using AKS cluster. This tool...
Read more >openshift prometheus grafana dashboard
Provide built-in security and enterprise readiness: As EclipseChe becomes a ... Kubernetes services menu in the Azure portal and select your AKS cluster....
Read more >Newest 'azure-aks' Questions - Stack Overflow
Dashboard not reachable after successfully deploying eclipse che on AKS cluster. I am installing the eclipse che in AKS using chectl.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Thanks, @karatkep @tolusha for the support. Finally, dashboard opened up. I had to hit swagger API first “dashboard/api/swagger” and then afterward dashboard page also opened up. @karatkep , will wait for your response on how to configure oauth-proxy v7.4.0 with che AKS setup. The latest release of che is using 7.4.0 so it becomes very critical.
@kuldeeparora89 I don’t think so. Request flow is
nginx
->oauth-proxy
->traefik
->dashboard
You got 404 inoauth-proxy
logs.