Grpc/check #1
Open
Grpc/check #1
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
ldez
force-pushed
the
grpc/check
branch
10 times, most recently
from
dbcd0e6 to
e4a8ac6
Compare
kevinpollet
force-pushed
the
grpc/check
branch
from
0b31c8b to
6b8c133
Compare
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 does this PR do?
Add gRPC support to healthcheck (using "grpc" scheme in the backend config option). It's based on GRPC Health Checking Protocol v1
Motivation
We need to deploy gRPC apps that will not be immediately ready to serve data (populating caches, ...). This will allow Traefik to not route request to a "unhealthy" container.
See also traefik#6027
More
TestSetGrpcBackendsConfigurationAdditional Notes
This is probably a naive implementation, any help / comment is welcome !
PS: most changes are related to tests (192+ / 2-)