feat(health): add health endpoint#43
Open
andresromerodev wants to merge 1 commit intogoogleforgames:mainfrom
Open
feat(health): add health endpoint#43andresromerodev wants to merge 1 commit intogoogleforgames:mainfrom
andresromerodev wants to merge 1 commit intogoogleforgames:mainfrom
Conversation
Author
|
@joeholley This is my first PR, let me know if you need me to adjust anything, happy to do that! |
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
1 participant
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.
Summary
Adds a
/healthHTTP endpoint to Open Match 2 Core so it can register and operate correctly with load balancers across cloud providers, including AWS, Azure and others outside of GCP.Problem
Open Match 2 Core currently lacks a dedicated health check endpoint. Most managed load balancers outside of GCP, such as AWS ALB/NLB and Azure Application Gateway require an HTTP endpoint that responds with a
200 OKto confirm the service is alive and ready to receive traffic. Without it, OM Core pods fail target group health checks, are never marked as healthy, and receive no traffic, making multi-cloud and hybrid deployments non-functional.