Web console: better management proxy detection #15453
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.
This PR tries to address a UX confusion where the console goes into "no management proxy mode" when in-fact the coordinator leader can simply not be determined in a transitive state. This is because right now the console relies on havign
/proxy/coordinator/status
return 200 to know that the management proxy is enabled. But that call might fail even when the management proxy is on.In this PR I add a
/proxy/enabled
endpoint that simply returns{"enabled":true}
and retool the console to use that route instead. Also I allow for a code 400 to indicate that the management proxy is running.