Expose agent readiness endpoint on nginx port #387
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.
Currently, all services except the agent and tracker have their health and readiness endpoints exposed on their nginx port. The agent's readiness endpoint is exposed by the agent server (a different server, not the nginx server!). To reach consistency across services, the agent's readiness endpoint should be exposed by its nginx server (on the nginx port).
To expose the readiness endpoint on the nginx server, we can reroute any requests to the nginx
/readiness
API to the agentserver, exactly like we already do for the/health
endpoint.Tested locally by building the devcluster: (16000 is the nginx port)