Ingress Operator is degraded with the reason "IngressUnavailable"
Issue
-
The Ingress Operator was failing with the below message:
"lastTransitionTime": "2024-08-19T08:10:08Z", "message": "The \"default\" ingress controller reports Available=False: IngressControllerUnavailable: One or more status conditions indicate unavailable: DeploymentAvailable=False (DeploymentUnavailable: The deployment has Available status condition set to False (reason: MinimumReplicasUnavailable) with message: Deployment does not have minimum availability.)", "reason": "IngressUnavailable", "status": "False", "type": "Available" -
Ingress router PODs are not running.
- The Ingress Cluster Operator is regarded during the OpenShift upgrade.
-
The router-default PODs are in the CrashLoopBackOff state due to the below error:
2024-08-19T08:05:42.752027900Z E0819 08:05:42.751993 1 metrics.go:132]metrics "msg"="listening on the metrics port failed" "error"="listen tcp 0.0.0.0:1936: bind: address already in use"
Environment
- Red Hat OpenShift Container Platform
- v4.14
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.