gRPC LoadBalancingPolicy Support #15861
Merged
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.
When using quarkus in kubernetes you currently will run into scaling issues if one service tries to connect to multiple backend grpc services. Kubernetes Headless services can solve this issue but in quarkus the load balancing policy can currently not be changes.
With this pull request it should add the
quarkus.grpc.clients."service-name".load-balancing-policyfield. The field will by default behave like it currently does.Possible options for the field include
pick_first(default),round_robin,grpclb.refs #9326