Multi-AZ OSD or ROSA cluster showing two instances of router pods
Environment
- Red Hat OpenShift Service on AWS (ROSA)
- 4
- Red Hat OpenShift Dedicated (OSD)
- 4
- Ingress Operator
Issue
- When configuring the Multi-AZ OSD or ROSA cluster, using Classic ELB, only 2 instances of router pods are running instead of 3.
- Is it possible to scale router pods on the Multi-AZ OSD or ROSA cluster configured using CLB.
Resolution
-
When configuring Multi-AZ ROSA using Classic ELB, It is expected to have two router pod instances, each running on one infra node as configured in the Load Balancer service.
-
Even if the cluster has three infra nodes, there will not be three replicas of the routers in the OSD/ROSA cluster environment as the default configuration for the number of routers in the OSD/ROSA cluster environments is two, and this default configuration cannot be changed.
Root Cause
-
By default, the replicas of the ingresscontrollers are 2 in OSD/ROSA environment.
-
It is not possible to configure/customize ingresscontroller in OSD/ROSA. Check Customize the ingresscontroller in OSD and ROSA
Diagnostic Steps
- To check the number of router pods. You can use for example the following command:
$ oc get -n openshift-ingress-operator ingresscontrollers default -o jsonpath='{$.status.availableReplicas}{"\n"}'
2
This solution is part of Red Hat’s fast-track publication program, providing a huge library of solutions that Red Hat engineers have created while supporting our customers. To give you the knowledge you need the instant it becomes available, these articles may be presented in a raw and unedited form.
Comments