-
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
[helm] Eclipse Che fail to start when using self-signed-cert on k8s #16429
Comments
@eder-santos chectl server:start --platform=k8s --multiuser --domain=10.96.0.1.nip.io --installer=helm --postgres-pvc-storage-class-name=local-storage --chenamespace=che |
Hi @tolusha
These are the secrets generated by helm:
|
@eder-santos |
Also |
Thanks @tolusha
|
|
Thanks @tolusha, feel free to ask me any question.
|
I see - name: CHE_SELF__SIGNED__CERT
valueFrom:
secretKeyRef:
key: ca.crt
name: che-tls
optional: false |
Did you use |
So root cause is that before deploying Eclipse Che the |
I assume that che namespace was not vanished properly before second installation |
Hi @tolusha
and then create again the namespace I'm not using the --self-signed-cert option, but I notice the env var is created even without that option. This is my start command
Let me know if you need more information, thank you |
@eder-santos |
Meanwhile you can try to deploy on minikube [1] cluster. |
Thank you @tolusha I will try it |
@eder-santos have you succeeded with any of the installation methods? |
Hi @mmorhun |
@eder-santos Minikube installation is designed to try it on single machine or for development purposes. The same I may say about CRC, but there are some tries to make it accessible outside. You may take a look at this one. Can you try to deploy Che as you described in the issue description but using |
@eder-santos |
@eder-santos |
Describe the bug
I'm trying to deploy Eclipse Che on a Kubernetes cluster using self-signed-cert and the helm installer, after following the doc the problem persists.
Che version
Steps to reproduce
Create a namespace:
kubectl create namespace che
Set environment variables:
/etc/profile.d/che.sh
chectl server:start --platform=k8s --multiuser --domain=10.96.0.1.nip.io --installer=helm --postgres-pvc-storage-class-name=local-storage --chenamespace=che --tls --self-signed-cert
Expected behavior
Eclipse che should be deployed correctly
Runtime
Kubectl version
oc version
)minikube version
andkubectl version
)minishift version
andoc version
)docker version
andkubectl version
)Screenshots
Installation method
Environment
Eclipse Che Logs
Additional context
Possible duplicates #16396, #16280
Also could you please tell if there is any way to use a non nightly version, I need a stable version for production enviroment.
The text was updated successfully, but these errors were encountered: