feat(mpc-operator-check): add kms-core /config to health check#30
Merged
Conversation
piizama
force-pushed
the
piizama/mpc-check-update
branch
4 times, most recently
from
baa67ad to
f4c38a6
Compare
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
piizama
force-pushed
the
piizama/mpc-check-update
branch
from
f4c38a6 to
fc30edb
Compare
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.
Adds the kms-core
/configendpoint output to the operator health check for troubleshooting and ruling out misconfigs.The check fetches the running config (JSON) from the telemetry server at
kms-core-<id>:9646/config(added in zama-ai/kms#425), printed alongside the static config files before the health check runs. A fetch failure is non-fatal so it never masks the health-check result.Closes zama-ai/infra-internal#107