-
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
incubator/crd.yaml tlsSupport:true by default breaks server:start in minikube #16409
Comments
@gattytto could you please provide step by step flow how you tried to deploy Che. Also full logs attached increases chances of problem understanding. |
Duplicates |
just emptied out /usr/local/lib/chectl and deleted /usr/local/bin/chectl then it downloads all the yamls again and puts the chectl binary in place, then run it using: as mentioned, those 2 settings come by default in the crd.yaml file downloaded by the script. Switching tlsSupport back to "false" allowed me to deploy che normally. |
@gattytto |
@tolusha tlsSupport is still enabled by default along with selfSigned set to false, meaning chectl+che-operator+kube will try tls without expecting self signed (I'm guessing self signed will still be used by default) so this will break? |
@gattytto |
changes introduced in latest versions of chectl the file:
/usr/local/lib/chectl/templates/che-operator/crds/org_v1_che_cr.yaml
set the following default:
while the comment above tlsSupport instates:
# TLS mode for Che. Make sure you either have public cert, or set selfSignedCert to true
after issuing "chectl server:start -m -p minikube" to start a new che, che-server breaks on startup because of:
The text was updated successfully, but these errors were encountered: