Add SNI bypass for reverse proxy health checks#364
Open
KashDev00 wants to merge 1 commit into
Open
Conversation
William-Edwards-STFC
approved these changes
Jul 3, 2026
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
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.
This PR adds an SNI bypass for the reverse proxy health check.
The health check module does not add an SNI(server name indication) to the health check request.
Envoy expects the SNI to be present in the request. Without the SNI in the request envoy rejects the request, and the reverse proxy thinks the server is down.
Adding a default listener and an HTTP route, and a default listener without the hostname(no SNI required, if no hostname is checked) resolves the issue