-
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] Use default ingress TLS certificate if tls.secretName is not set #18259
Conversation
❌ E2E Happy path tests failed ❗ See Details
Tested with Eclipse Che Multiuser User on K8S (minikube v1.1.1)
|
[crw-ci-test --rebuild] |
❌ E2E Happy path tests failed ❗ See Details
Tested with Eclipse Che Multiuser User on K8S (minikube v1.1.1)
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I haven't tested but changes LGTM
Signed-off-by: Mykola Morhun <mmorhun@redhat.com>
Rebased |
❌ E2E Happy path tests failed ❗ See Details
Tested with Eclipse Che Multiuser User on K8S (minikube v1.1.1)
|
[crw-ci-test] |
❌ E2E Happy path tests failed ❗ See Details
Tested with Eclipse Che Multiuser User on K8S (minikube v1.1.1)
|
Here is the issue for the failing test |
@tolusha You're right..It's a known problem, which happens time to time. |
Signed-off-by: Mykola Morhun mmorhun@redhat.com
What does this PR do?
Makes it possible to use default cluster certificate for Helm installer.
What issues does this PR fix or reference?
Implements Helm part of #18079
Depends on: #17644 and che-incubator/chectl#963
How to test this PR?
Run
chectl server:deploy --platform=minikube --installer=helm --use-cluster-certificate
PR Checklist
As the author of this Pull Request I made sure that:
What issues does this PR fix or reference
andHow to test this PR
completedReviewers
Reviewers, please comment how you tested the PR when approving it.