tolusha
commented
2 years ago It might be the same reason https://github.com/eclipse/che/issues/20726
Closed sebastiankomander closed 2 years ago
tolusha
commented
2 years ago It might be the same reason https://github.com/eclipse/che/issues/20726
sebastiankomander
commented
2 years ago I tried patching che-dashboard-Ingress:
Name: che-dashboard
Namespace: eclipse-che
Address:
Default backend: default-http-backend:80
TLS:
che-tls terminates che-eclipse-che.mydomain.con
Rules:
Host Path Backends
---- ---- --------
che-eclipse-che.mydomain.com
/dashboard/* che-dashboard:8080 (1.2.3.4:1234)
Annotations: che.eclipse.org/managed-annotations-digest: NpIhR7gmyYZJ3KW2WvSw4lBBh-vqSAsF5n83BvCrMeE=
kubernetes.io/ingress.class: nginx
nginx.ingress.kubernetes.io/proxy-connect-timeout: 3600
nginx.ingress.kubernetes.io/proxy-read-timeout: 3600
nginx.ingress.kubernetes.io/ssl-redirect: true
nginx.ingress.kubernetes.io/use-regex: trueSame problem again..
sebastiankomander
commented
2 years ago I tried installer=operator, but che-dashboard-ingress looks wrong
kubectl describe ingress -n eclipse-che che-dashboard
---- ------ ---- ---- -------
Warning Rejected 41s nginx-ingress-controller All hosts are taken by other resources
Warning Rejected 41s nginx-ingress-controller All hosts are taken by other resources
I looks like the problem ist located in che-ingress. The ingress catches all from "/". So che-dashboard never gets activated and - as far as I can see trying with curl - every requests gets routed to che-ingress and then forwarded to "/dashboard". But /dashboard is getting caught by che-ingress and the redirect starts from beginning. I keep tryining with helm-installer...
sebastiankomander
commented
2 years ago Ok, problem lies within the ingress installation. If you use an old version of nginx-ingress (v0.41.0) everything works finde. If you use the latest stable version it's not working - see my comment
martinelli-francesco
commented
2 years ago I've just installed Eclipse Che 7.41.2 and still have the same issue even though I followed the instructions (https://www.eclipse.org/che/docs/che-7/installation-guide/installing-che-on-microsoft-azure/) that install nginx-ingress (v0.41.0): kubectl apply -f https://raw.githubusercontent.com/kubernetes/ingress-nginx/controller-**v0.41.0**/deploy/static/provider/cloud/deploy.yaml
I get redirected to
tolusha
commented
2 years ago Could you try configure Eclipse Che to use single-host strategy?
kubectl patch checluster/eclipse-che -n eclipse-che --type=json -p '[{"op": "replace", "path": "/spec/server/serverExposureStrategy", "value": "single-host"}]'
kubectl patch checluster/eclipse-che -n eclipse-che --type=json -p '[{"op": "replace", "path": "/spec/k8s/singleHostExposureType", "value": "gateway"}]'
csa-nathan
commented
2 years ago I've just installed Eclipse Che 7.41.2 and still have the same issue even though I followed the instructions (https://www.eclipse.org/che/docs/che-7/installation-guide/installing-che-on-microsoft-azure/) that install nginx-ingress (v0.41.0): kubectl apply -f https://raw.githubusercontent.com/kubernetes/ingress-nginx/controller-**v0.41.0**/deploy/static/provider/cloud/deploy.yaml
I get redirected to /dashboard/ which returns with 200 but for all the resources (branding.css, loader.svg, ...) I get a 404.
Try and remove the Che Dashboard Ingress Path from /dashboard/ to just /dashboard
It should work.
che-bot
commented
2 years ago Issues go stale after 180 days of inactivity. lifecycle/stale issues rot after an additional 7 days of inactivity and eventually close.
Mark the issue as fresh with /remove-lifecycle stale in a new comment.
If this issue is safe to close now please do so.
Moderators: Add lifecycle/frozen label to avoid stale mode.
Describe the bug
Infrastructure:
Tried multiple variants: chectl server:deploy --installer=operator --platform=k8s --domain=
chectl server:deploy --installer=operator --platform=k8s --domain= --multiuser
chectl server:deploy --installer=helm --platform=k8s --domain=
chectl server:deploy --installer=helm --platform=k8s --domain= --multiuser
Deployment is successfull and plugin registry, devfile registry, keycloak are working and reachable. If I navigate to dashboard (mydomain.com/dashboard) every browser (testes chrome and mozilla in different versions) if get "Too many redirects"
Request-URL: https://che-eclipse-che.vwtg.cloud.suedleasing-dev.com/dashboard/ Response Header: Location: /dashboard/
Tried with chectl/0.0.20211104-next.393086a linux-x64 node-v12.22.7 chectl/7.38.1 linux-x64 node-v12.22.7
Same result
Che version
other (please specify in additional context)
Steps to reproduce
Expected behavior
Dashboard up an running
Runtime
Kubernetes (vanilla)
Screenshots
No response
Installation method
chectl/latest
Environment
Azure
Eclipse Che Logs
Additional context
No response