Added missing healthcheck port exposure command#687
Added missing healthcheck port exposure command#687thatcherhubbard wants to merge 2 commits intorh-mobb:mainfrom
Conversation
✅ Deploy Preview for rh-cloud-experts ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
diana-sari
left a comment
diana-sari
left a comment
There was a problem hiding this comment.
Ah good catch thanks very much for flagging this!:)
i think the health check port exposure is already covered in the create-private-ingress-controller referenced in Step 2, so rather than repeating the full patch command here, should we may be just tighten Step 2 to explicitly call out to complete the inner NLB setup through the service patch and health-check exposure before continuing?
So for Step 2, we can do something like this for example, what do you think?
Follow the Private Ingress Controller with ALB guide to create the private IngressController and inner NLB.
Complete that guide through the point where:
- the IngressController service has been patched to expose the router health check port (1936)
- the inner NLB is healthy
- you have retrieved the private IP addresses of the inner NLB targets
You will use those IPs in the next step when creating the outer target group/NLB for CloudFront.
|
Btw, i tried pushing the fix directly but don't have the permission to update your fork, so i opened a follow-up PR against your branch thatcherhubbard#1 |
2 participants
The procedure was missing the command to make it possible to reach the
IngressControllerhealthcheck port from outside the cluster by adding it to theService.