-
Notifications
You must be signed in to change notification settings - Fork 62
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
feat: set probe scheme to HTTPS when TLS is enabled #144
Conversation
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.
Thanks for the PR 🙏
Can you please increment the chart version in the Chart.yaml?
Also, if we enable the probes in the self-signed example, the tests should pass, right?
Do want a patch bump to 7.2.1? And yes, if we implement this, and enable the probes in the self-signed example, the probes will succeed. |
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.
Nice, this seems to work 👍
Thank you @PurseChicken 🎉
* Change scheme to HTTPS on probes when TLS is enabled. * Fix issue with potential NIL pointer if TLS is undefined. * bump minor version of chart and update to latest appVersion * Remove disabling probes from self-signed example * Use deepCheck helper for TLS.Enabled * Add newline to chart.yaml so linting succeeds
This fixes #143
Definition of Ready
This PR sets the liveliness, readiness and startup probe schemes to HTTPS if TLS is enabled in configmapConfig.
Without setting scheme: HTTPS it defaults to HTTP which causes the probes to fail and the pod(s) never report as healthy.