From 56ad35a8fae3ff3b32817a5c100b3effffa5f9f3 Mon Sep 17 00:00:00 2001 From: thatcherhubbard Date: Thu, 5 Mar 2026 10:53:01 -0800 Subject: [PATCH 1/2] Added missing healthcheck port exposure command --- content/rosa/nlb-cf-vpco/index.md | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/content/rosa/nlb-cf-vpco/index.md b/content/rosa/nlb-cf-vpco/index.md index 313616306..ce73ec89b 100644 --- a/content/rosa/nlb-cf-vpco/index.md +++ b/content/rosa/nlb-cf-vpco/index.md @@ -125,6 +125,13 @@ Under **Listeners and routing**, select protocol **TCP** on port **443**, and fo Next, click **Create load balancer** button at the bottom of the page. It will take a couple of minutes for the status to turn from **Provisioning** to **Active**. Then, copy the **Load balancer ARN** as you would need it for the next step. +### 4.4 Expose Healthceck Port + +The custom port and path for the healthcheck override isn't reachable from outside the cluster by default, which means none of the backends in the target group will show up as 'Healthy' until it's resolved, which can be done with a simple `oc patch` command. Note that the name of the service referred to as a variable should match the service name for the `IngressController` created earlier: + +```bash +oc -n openshift-ingress patch svc ${INGRESS_SERVICE_NAME} -p '{"spec":{"ports":[{"port":1936,"targetPort":1936,"protocol":"TCP","name":"httphealth"}]}}' +``` ## 5. Create CloudFront VPC Origin and Distribution From 353231c69fe2544b466965e66bcfac250b95382c Mon Sep 17 00:00:00 2001 From: thatcherhubbard Date: Thu, 5 Mar 2026 14:29:30 -0800 Subject: [PATCH 2/2] Fixing typo --- content/rosa/nlb-cf-vpco/index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/rosa/nlb-cf-vpco/index.md b/content/rosa/nlb-cf-vpco/index.md index ce73ec89b..495d7d06f 100644 --- a/content/rosa/nlb-cf-vpco/index.md +++ b/content/rosa/nlb-cf-vpco/index.md @@ -125,7 +125,7 @@ Under **Listeners and routing**, select protocol **TCP** on port **443**, and fo Next, click **Create load balancer** button at the bottom of the page. It will take a couple of minutes for the status to turn from **Provisioning** to **Active**. Then, copy the **Load balancer ARN** as you would need it for the next step. -### 4.4 Expose Healthceck Port +### 4.4 Expose Healthcheck Port The custom port and path for the healthcheck override isn't reachable from outside the cluster by default, which means none of the backends in the target group will show up as 'Healthy' until it's resolved, which can be done with a simple `oc patch` command. Note that the name of the service referred to as a variable should match the service name for the `IngressController` created earlier: