istio-ingressgatway and istio-egressgateway pods remain in CreateContainerConfigError status in OpenShift 4

Solution Verified - Updated -

Issue

  • When deploying a new ServiceMeshControlPlane the "istio-ingressgateway" and "istio-egressgateway" pods never start:
NAME                                            READY   STATUS                       RESTARTS   AGE
grafana-xxxxxxxxx-xxxxx                        2/2     Running                      0          7d16h
istio-egressgateway-xxxxxxxxx-xxxxx            0/1     CreateContainerConfigError   0          7d16h
istio-ingressgateway-xxxxxxxxx-xxxxx           0/1     CreateContainerConfigError   0          7d16h
istiod-elms-istiosystem-mesh-xxxxxxxxx-xxxxx   1/1     Running                      0          7d16h
jaeger-xxxxxxxxx-xxxxx                         2/2     Running                      0          3h54m
prometheus-xxxxxxxxx-xxxxx                     2/2     Running                      0          7d16h

Environment

  • OpenShift Container Platform (OCP)
    • 4.9 and later
  • Red Hat OpenShift ServiceMesh
    • 2.1 and later

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content