fix(registry): change readiness and liveness probe to httpGet /v2 #720
Conversation
This file contains hidden or 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
This commit ensures that the liveness and readiness probes are targeted to httpGet on the /v2 path to avoid TLS handshake errors Signed-off-by: abhijith-darshan <[email protected]>
abhijith-darshan
changed the title
Skarlso
approved these changes
Aug 13, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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 this PR does / why we need it
There are lot of error logging and noise in the registry deployment due to TLS errors on the probes
httpGeton/v2path to avoid TLS handshake errorsAdditionally there are noises from OTEL metrics (enabled by default in registry) but they can be overridden with env via values
This is a very small fix and may not fit into v2 controllers but until then it would be nice to get this fix in.