feat: Allow using self-signed certificates in HTTPS health tests #39
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Usually, the container's HTTPS ports use self-signed certificates instead of real ones. This makes the HTTPS health check always fail and be retried.
This PR allows self-signed certificates for health checks.
I think for health-checks it's an acceptable trade-off but I'm open for getting even better ideas that solve the underlying problem (HTTPS health-checks being almost useless).
Thanks for your time! 👋