Fix ProxyKube
not reporting its readiness
#12150
Merged
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.
After #11249 the
/readyz
diag endpoint will only report OK if enough components have heartbeated without error; however, theproxy.kube
service will not actually heartbeat unless it's running in "legacy" mode, also acting as akubernetes_service
. This PR makes it so that if that's the case, an initial OK heartbeat is reported for that component (similarly to what adb_service
will do when running in dynamic mode with no configured databases).Fixes #12139.