fix: Use micronaut healthcheck path for liveness and readiness probes #62
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
What changes are being made and why?
We recently experienced unintended Kestra pod restarts in our Kubernetes cluster. After analysis we discovered that this was due to a misconfigured liveness probe in the Helm chart. The probe was pointing to
/health, which depends on external components of the pod. This caused the pod to be restarted by Kubernetes when an external component was unavailable.To resolve this, we updated the value file to configure the liveness and readiness probes to use the correct Micronaut health paths:
/health/liveness/health/readinessThis ensures that the probes accurately reflect the health of the java application itself.
This will resolve issue #20