Service Mesh ServiceEntry for external TCP services routes traffic to a single endpoint

Solution In Progress - Updated -


When a ServiceEntry for TCP service is set without an address field and the resolution is set to DNS, then all connections on a port defined in such ServiceEntry are not routed by hostname.

Configuring ExternalService instead of ServiceEntry leads to the similar result.

TLS services work as expected.


  • Red Hat OpenShift Container Platform 4.x
  • OpenShift Service Mesh

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