Getting started Community Training Tutorials Documentation APIs, AI & Tools
-
Kubernetes
-
OpenShift
kubectl get pods -n <omni-gateway-namespace>
oc get pods -n <omni-gateway-namespace>
Managed Omni Gateway on Runtime Fabric inherits the forward proxy settings of Runtime Fabric. If your Runtime Fabric cluster reaches the internet through a forward proxy, Managed Omni Gateway uses the same proxy automatically. You don’t need to configure a forward proxy for each gateway.
To configure the proxy for Runtime Fabric, see Configuring Proxies on Runtime Fabric.
Only HTTP connections route through the forward proxy.
The following connections route through the forward proxy:
Connections to Anypoint Platform
Outbound policy connections
Connections to upstream services
HTTP (Fluent Bit) log connections
Using the noProxy parameter, you can configure HTTP and HTTPS connections to connect directly without using the forward proxy.
Configuring a forward proxy does not alter these connections:
Connections to shared storage
Lightweight Directory Access Protocol (LDAP) connections
Non-HTTP log connections
Make sure that:
The forward proxy allows the hosts and ports listed in Requirements and Limits for Omni Gateway for your control plane.
The forward proxy doesn’t inspect TLS traffic (SSL passthrough) on the endpoints that use mTLS. These endpoints include:
The Anypoint Platform control plane endpoints that the Runtime Fabric agent connects to. Managed Omni Gateway receives its configuration through the Runtime Fabric agent.
The external endpoints that Managed Omni Gateway connects to over mTLS, such as Anypoint Monitoring.
For the endpoints that require SSL passthrough, see Requirements and Limits for Omni Gateway.
Optionally, to confirm that the Managed Omni Gateway reaches external hosts through the forward proxy:
Find the egress gateway pod:
Kubernetes
OpenShift
kubectl get pods -n <omni-gateway-namespace>
oc get pods -n <omni-gateway-namespace>
Check the connection to an external upstream:
Kubernetes
OpenShift
kubectl exec -n <omni-gateway-namespace> <omni-egress-pod> -c app -- flexctl check http https://<upstream-host>
oc exec -n <omni-gateway-namespace> <omni-egress-pod> -c app -- flexctl check http https://<upstream-host>