chore: Switch liveness probe to tcp socket instead of httpGet #637
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
In SUP-159 a customer wanted to enable security for the Namenode HTTP API.
This resulted in
/dfshealth.html
returning a 401 instead of a 200 - thus failing the liveness probe.This PR allows customers to configOverride security for the HTTP APIs (hopefully until we support them natively)
We intentionally did not write a curl script that checks for 200 or 401 but just went with the TCP port.
Definition of Done Checklist
Author
Reviewer
Acceptance