-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Che is not accessible after being started by chectl on Kubernetes #13840
Comments
I've just quickly tried this with minikube with kvm2 driver and "plain" Console output:
╭─rhopp@localhost ~ ╭─rhopp@localhost ~ ╭─rhopp@localhost ~ ╭─rhopp@localhost ~ ╭─rhopp@localhost ~ Have you manage to reproduce somewhere else, than on virtualized openstack machine? |
yes on my computer I don't reproduce as well could you retry by cleaning up $HOME/.minikube folder before starting minikube |
There was no such an error with |
I would also notice that |
@dmytro-ndp is it possible to get access to this environment ? |
Issues go stale after Mark the issue as fresh with If this issue is safe to close now please do so. Moderators: Add |
I'm still having the same issue.
How do I make I'll gladly give anymore information that is needed. |
Describe the bug
Chectl didn't enable ingress addon on Kubernetes besides there was
Enable minikube ingress addon [completed]
in output, and it made Che inaccessible by Che Server URL.Chectl version
https://github.com/che-incubator/chectl/releases/latest/download/chectl-linux
Steps to reproduce
Expected behavior
Che has been installed and is accessible by Che Server URL.
Actual behavior
Che was not accessible by Che Server URL because ingress addon was not actually enabled:
There was no ~/.minikube/config/config.json file with
"ingress": true
parameterThere was no nginx-ingress-controller running among the pods:
Runtime
Logs
Full build log: https://codeready-workspaces-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/che7-e2e-tests/job/CHE-7-Happy-Path-Tests/338/
Installation method
Environment
The text was updated successfully, but these errors were encountered: