[sui_proxy/pod health] #19416
Merged
[sui_proxy/pod health] #19416
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
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
3 Skipped Deployments
|
|
will this be a health or ready check? |
## Description * add a route for pod health in k8s i am using the consumer_operations_submitted value but more values can be added later if we need to. when this value is non-zero, it means the service is processing data correctly and can be used to consider it healthy enough to handle traffic. ## Test Plan local
johnjmartin
reviewed
Sep 18, 2024
johnjmartin
approved these changes
Sep 18, 2024
suiwombat
force-pushed
the
jh/sui_proxy_health_check
branch
from
1e85733
to
802eee1
Compare
liveness |
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.
Description
i am using the consumer_operations_submitted value but more values can be added later if we need to. when this value is non-zero, it means the service is processing data correctly and can be used to consider it healthy enough to handle traffic. it will be implemented as a liveness check.
Test Plan
local
Release notes
Check each box that your changes affect. If none of the boxes relate to your changes, release notes aren't required.
For each box you select, include information after the relevant heading that describes the impact of your changes that a user might notice and any actions they must take to implement updates.