Routing Application Egress Traffic via Egress Gateway Using Destination IP Address in a Service Mesh

Solution Verified - Updated -

Issue

  • In OpenShift Service Mesh (OSSM), there is a requirement for application egress traffic to exit through the Istio egressgateway pod when accessing external services via destination IP addresses.
  • When the application initiates outbound connections using a destination IP address instead of a hostname, it is necessary to determine whether OSSM can be configured to route this traffic through the Istio egressgateway pod.

Environment

  • Red Hat OpenShift Container Platform
    • 4
  • Red Hat OpenShift Service Mesh
    • 3

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