Elasticsearch operator reports x509 errors communicating with ElasticSearch in OpenShift Service Mesh project.

Solution In Progress - Updated -


  • The elasticsearch operator throws x509 errors for the instance deployed in the OpenShift Service Mesh project.
  • The following command displays the status as "cluster health unknown"

    oc get elasticsearch  -A -o=custom-columns=NAMESPACE:.metadata.namespace,NAME:.metadata.name,STATUS:.status.cluster.status
    NAMESPACE           NAME            STATUS
    istio-system        elasticsearch   cluster health unknown
    can-istio-system    elasticsearch   cluster health unknown
    ics-atwistio2       elasticsearch   cluster health unknown
    openshift-logging   elasticsearch   green
  • This issue is observed when there are multiple OpenShift Service Mesh control planes deployed.


  • Red Hat OpenShift Container Platform
    • 4.5
  • Red Hat OpenShift Service Mesh
    • 1.x

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