此内容没有您所选择的语言版本。

Chapter 3. Directing outbound traffic through a gateway

Using Istio APIs, you can configure gateway proxies that were installed using gateway injection to direct traffic that is bound for an external service.

3.1. About directing egress traffic through a gateway
复制链接

You can configure a gateway installed through gateway injection as an exit point for traffic leaving the service mesh. It acts as a forward proxy for requests sent to services external to the mesh.

Egress gateway

An egress gateway is configured as an exit point for traffic leaving the service mesh, acting as a forward proxy for requests sent to external services. You can configure an egress gateway to fulfill security requirements:

Traffic Restrictions: In environments with strict traffic restrictions, an egress gateway ensures all outbound traffic flows through a dedicated set of nodes.
Network Policy Enforcement: When network policies prevent application nodes from directly accessing external services, the egress gateway handles the external access.

In these scenarios, gateway proxies are deployed on dedicated egress nodes capable of accessing external services. These nodes can then be subjected to strict network policy enforcement or additional monitoring to enhance security.

Configure egress traffic

You can configure a gateway installed through gateway injection to direct the egress traffic by combining the following Istio resources:

Use the ServiceEntry resource to define the properties of an external service. The external service is added to the Istio service registry for the mesh, which enables you to apply Istio features, such as monitoring and routing rules, to the traffic exiting the mesh that is destined for an external service.
Use the Gateway, VirtualService, and DestinationRule resources to set up rules that route traffic from the mesh to the external service using the gateway proxy.

Egress routing in ambient mode

If your deployment uses ambient mode, you must configure egress routing using the Kubernetes Gateway API instead of Istio Gateway and VirtualService resources. The Kubernetes Gateway API provides a standardized, Kubernetes-native method for defining how traffic exits the mesh and reaches external services.

You can use Gateway and HTTPRoute (or GRPCRoute) resources to control how mesh traffic is routed to destinations outside the cluster. The Gateway API is fully supported in ambient mode and can also be used with sidecar-based deployments, providing a consistent configuration model for both ingress and egress routing.

3.2. Directing egress traffic through a gateway using Istio APIs
复制链接

Use Istio APIs to direct outbound HTTP traffic through a gateway that was installed using gateway injection.

Prerequisites

You have installed a gateway using gateway injection.

Procedure

Create a namespace called curl by running the following command:
```
oc create namespace curl
```
```
$ oc create namespace curl
```
Copy to Clipboard Toggle word wrap
Depending on the update strategy you are using, enable sidecar injection in the namespace by running the appropriate commands:
1. If you are using the InPlace update strategy, run the following command:
  $ oc label namespace curl istio-injection=enabled
  Copy to Clipboard Toggle word wrap
2. If you are using the RevisionBased update strategy, run the following commands:
  1. Display the revision name by running the following command:
    
    $ oc get istiorevisions.sailoperator.io
    
    Copy to Clipboard Toggle word wrap
    
    Example output
    
    NAME TYPE READY STATUS IN USE VERSION AGE default Local True Healthy True v1.24.3 3m33s
    
    Copy to Clipboard Toggle word wrap
  2. Label the namespace with the revision name to enable sidecar injection by running the following command:
    
    $ oc label namespace curl istio.io/rev=default
    
    Copy to Clipboard Toggle word wrap

Deploy a curl application by running the following command:

oc apply -n curl -f https://raw.githubusercontent.com/openshift-service-mesh/istio/refs/heads/master/samples/curl/curl.yaml

$ oc apply -n curl -f https://raw.githubusercontent.com/openshift-service-mesh/istio/refs/heads/master/samples/curl/curl.yaml

Copy to Clipboard

Toggle word wrap

Export a CURL_POD environment variable that has been initialized with the name of the curl pod:

export CURL_POD=$(oc get pod -n curl -l app=curl -o jsonpath='{.items[0].metadata.name}')

$ export CURL_POD=$(oc get pod -n curl -l app=curl -o jsonpath='{.items[0].metadata.name}')

Copy to Clipboard

Toggle word wrap

Create a YAML file named http-se.yaml that directs traffic from the mesh to an external service. The following example defines a ServiceEntry for a URL.

apiVersion: networking.istio.io/v1
kind: ServiceEntry
metadata:
  name: egress-se
  namespace: curl
spec:
  hosts:
    - docs.redhat.com
  ports:
    - number: 80
      name: http-port
      protocol: HTTP
  location: MESH_EXTERNAL
  resolution: DNS

apiVersion: networking.istio.io/v1
kind: ServiceEntry
metadata:
  name: egress-se
  namespace: curl
spec:
  hosts:
    - docs.redhat.com
  ports:
    - number: 80
      name: http-port
      protocol: HTTP
  location: MESH_EXTERNAL
  resolution: DNS

Copy to Clipboard

Toggle word wrap

Apply the YAML file by running the following command:
```
oc apply -f http-se.yaml
```
```
$ oc apply -f http-se.yaml
```
Copy to Clipboard Toggle word wrap
Ensure the ServiceEntry configuration was applied correctly. Send an HTTP request to the host that you specified in the previous step by running the following command:
```
oc exec "$CURL_POD" -n curl -c curl -- curl -sSL -o /dev/null -D - http://docs.redhat.com
```
```
$ oc exec "$CURL_POD" -n curl -c curl -- curl -sSL -o /dev/null -D - http://docs.redhat.com
```
Copy to Clipboard Toggle word wrap
This command should return HTTP status codes, such as 301 (redirect) or 200 (success), indicating that the connection works.

Create a YAML file named http-gtw.yaml that creates an egress Gateway and routes traffic from the mesh to the host specified for the external service.

apiVersion: networking.istio.io/v1alpha3
kind: Gateway
metadata:
  name: egress-gw
  namespace: <gateway_namespace> # Namespace where the egress gateway is deployed
spec:
  selector:
    istio: <gateway_name> # Selects the egress-gateway instance to handle this traffic
  servers:
    - port:
        number: 80
        name: http
        protocol: HTTP
      hosts:
        - docs.redhat.com # External service host, not a full URL.
---
apiVersion: networking.istio.io/v1alpha3
kind: DestinationRule
metadata:
  name: egress-dr
  namespace: <gateway_namespace> # Namespace where the egress gateway is deployed
spec:
  host: <gateway_name>.<gateway_namespace>.svc.cluster.local
  subsets:
    - name: rh-docs

apiVersion: networking.istio.io/v1alpha3
kind: Gateway
metadata:
  name: egress-gw
  namespace: <gateway_namespace> # Namespace where the egress gateway is deployed
spec:
  selector:
    istio: <gateway_name> # Selects the egress-gateway instance to handle this traffic
  servers:
    - port:
        number: 80
        name: http
        protocol: HTTP
      hosts:
        - docs.redhat.com # External service host, not a full URL.
---
apiVersion: networking.istio.io/v1alpha3
kind: DestinationRule
metadata:
  name: egress-dr
  namespace: <gateway_namespace> # Namespace where the egress gateway is deployed
spec:
  host: <gateway_name>.<gateway_namespace>.svc.cluster.local
  subsets:
    - name: rh-docs

Copy to Clipboard

Toggle word wrap

Apply the YAML file by running the following command:
```
oc apply -f http-gtw.yaml
```
```
$ oc apply -f http-gtw.yaml
```
Copy to Clipboard Toggle word wrap

Create a YAML file named http-vs.yaml that sets up a VirtualService to manage the flow of traffic from the application sidecars through the egress gateway to the external host.

apiVersion: networking.istio.io/v1alpha3
kind: VirtualService
metadata:
  name: egress-vs
  namespace: curl # Namespace where the curl pod is running
spec:
  hosts:
    - docs.redhat.com # External service host, not a full URL.
  gateways:
    - mesh
    - <gateway_namespace>/egress-gw # Egress gateway name defined in the file that you used in the previous step.
  http:
    - match:
        - gateways:
            - mesh
          port: 80
      route:
        - destination:
            host: <gateway_name>.<gateway_namespace>.svc.cluster.local
            subset: rh-docs
            port:
              number: 80
          weight: 100
    - match:
        - gateways:
            - <gateway_namespace>/egress-gw # Egress gateway name defined in the file that you used in the previous step.
          port: 80
      route:
        - destination:
            host: docs.redhat.com
            port:
              number: 80
          weight: 100

apiVersion: networking.istio.io/v1alpha3
kind: VirtualService
metadata:
  name: egress-vs
  namespace: curl # Namespace where the curl pod is running
spec:
  hosts:
    - docs.redhat.com # External service host, not a full URL.
  gateways:
    - mesh
    - <gateway_namespace>/egress-gw # Egress gateway name defined in the file that you used in the previous step.
  http:
    - match:
        - gateways:
            - mesh
          port: 80
      route:
        - destination:
            host: <gateway_name>.<gateway_namespace>.svc.cluster.local
            subset: rh-docs
            port:
              number: 80
          weight: 100
    - match:
        - gateways:
            - <gateway_namespace>/egress-gw # Egress gateway name defined in the file that you used in the previous step.
          port: 80
      route:
        - destination:
            host: docs.redhat.com
            port:
              number: 80
          weight: 100

Copy to Clipboard

Toggle word wrap

Apply the YAML file by running the following command:
```
oc apply -f http-vs.yaml
```
```
$ oc apply -f http-vs.yaml
```
Copy to Clipboard Toggle word wrap

Resend the HTTP request to the URL:

oc exec "$CURL_POD" -n curl -c curl -- curl -sSL -o /dev/null -D - http://docs.redhat.com

$ oc exec "$CURL_POD" -n curl -c curl -- curl -sSL -o /dev/null -D - http://docs.redhat.com

Copy to Clipboard

Toggle word wrap

The terminal should display information similar to the following output:

...
HTTP/1.1 301 Moved Permanently
...
location: <example_url>
...

HTTP/2 200
Content-Type: text/html; charset=utf-8

...
HTTP/1.1 301 Moved Permanently
...
location: <example_url>
...

HTTP/2 200
Content-Type: text/html; charset=utf-8

Copy to Clipboard

Toggle word wrap

Ensure that the request was routed through the gateway by running the following command:

oc logs deployment/<gateway_name> -n <gateway_namespace> | tail -1

$ oc logs deployment/<gateway_name> -n <gateway_namespace> | tail -1

Copy to Clipboard

Toggle word wrap

Note

Access logging must be enabled for this verification step to work. You can enable access logging to the standard output by setting the spec.values.meshConfig.accessLogFile field to /dev/stdout in the Istio resource.

The terminal should display information similar to the following output:

[2024-11-07T14:35:52.428Z] "GET / HTTP/2" 301 - via_upstream - "-" 0 0 24 24 "10.128.2.30" "curl/8.11.0" "79551af2-341b-456d-b414-9220b487a03b" "docs.redhat.com" "23.55.176.201:80" outbound|80||docs.redhat.com 10.128.2.29:49766 10.128.2.29:80 10.128.2.30:38296 -

[2024-11-07T14:35:52.428Z] "GET / HTTP/2" 301 - via_upstream - "-" 0 0 24 24 "10.128.2.30" "curl/8.11.0" "79551af2-341b-456d-b414-9220b487a03b" "docs.redhat.com" "23.55.176.201:80" outbound|80||docs.redhat.com 10.128.2.29:49766 10.128.2.29:80 10.128.2.30:38296 -

Copy to Clipboard

Toggle word wrap

3.3. Directing egress traffic through a gateway by using the Kubernetes Gateway API
复制链接

Use the Kubernetes Gateway API to direct outbound HTTP traffic through an egress gateway.

Prerequisites

You installed an Istio control plane.
You configured the Istio and IstioCNI resources.

Procedure

Optional: Enable the Kubernetes Gateway API custom resource definitions (CRDs).

Note

As of Kubernetes 1.28 and OpenShift Container Platform 4.18 or earlier version of Red Hat OpenShift Service Mesh, the Kubernetes Gateway API CRDs are not available by default and you must install the CRDs before you can use them. OpenShift Container Platform 4.19 and later versions install the CRDs by default.

Create a YAML file named gateway-cr.yaml that enables the Kubernetes Gateway API CRDs.

apiVersion: gateway.networking.k8s.io/v1
kind: Gateway
metadata:
  name: bookinfo-gateway
spec:
  gatewayClassName: istio
  listeners:
  - name: http
    port: 80
    protocol: HTTP
    allowedRoutes:
      namespaces:
        from: Same
---
apiVersion: gateway.networking.k8s.io/v1
kind: HTTPRoute
metadata:
  name: bookinfo
spec:
  parentRefs:
  - name: bookinfo-gateway
  rules:
  - matches:
    - path:
        type: Exact
        value: /productpage
    - path:
        type: PathPrefix
        value: /static
    - path:
        type: Exact
        value: /login
    - path:
        type: Exact
        value: /logout
    - path:
        type: PathPrefix
        value: /api/v1/products
    backendRefs:
    - name: productpage
      port: 9080

apiVersion: gateway.networking.k8s.io/v1
kind: Gateway
metadata:
  name: bookinfo-gateway
spec:
  gatewayClassName: istio
  listeners:
  - name: http
    port: 80
    protocol: HTTP
    allowedRoutes:
      namespaces:
        from: Same
---
apiVersion: gateway.networking.k8s.io/v1
kind: HTTPRoute
metadata:
  name: bookinfo
spec:
  parentRefs:
  - name: bookinfo-gateway
  rules:
  - matches:
    - path:
        type: Exact
        value: /productpage
    - path:
        type: PathPrefix
        value: /static
    - path:
        type: Exact
        value: /login
    - path:
        type: Exact
        value: /logout
    - path:
        type: PathPrefix
        value: /api/v1/products
    backendRefs:
    - name: productpage
      port: 9080

Copy to Clipboard

Toggle word wrap

Apply the YAML file by running the following command:
```
oc apply -f gateway-cr.yaml
```
```
$ oc apply -f gateway-cr.yaml
```
Copy to Clipboard Toggle word wrap

Create a namespace called egress-gateway by running the following command:
```
oc create namespace egress-gateway
```
```
$ oc create namespace egress-gateway
```
Copy to Clipboard Toggle word wrap
Apply the istio-injection label to the namespace by running the following command:
```
oc label namespace egress-gateway istio-injection=enabled
```
```
$ oc label namespace egress-gateway istio-injection=enabled
```
Copy to Clipboard Toggle word wrap

Create a YAML file named egress-gateway-cr.yaml that defines the egress gateway.

# ServiceEntry to allow traffic to httpbin.org
apiVersion: networking.istio.io/v1
kind: ServiceEntry
metadata:
  name: httpbin-ext
spec:
  hosts:
  - httpbin.org
  ports:
  - number: 80
    name: http
    protocol: HTTP
  location: MESH_EXTERNAL
  resolution: DNS
---
# Gateway API Gateway for egress
apiVersion: gateway.networking.k8s.io/v1
kind: Gateway
metadata:
  name: httpbin-egress-gateway
  annotations:
    networking.istio.io/service-type: ClusterIP
spec:
  gatewayClassName: istio
  listeners:
  - name: http
    hostname: httpbin.org
    port: 80
    protocol: HTTP
    allowedRoutes:
      namespaces:
        from: Same
---
# HTTPRoute to direct traffic from sidecars to the egress gateway
apiVersion: gateway.networking.k8s.io/v1
kind: HTTPRoute
metadata:
  name: direct-httpbin-to-egress-gateway
spec:
  parentRefs:
  - kind: ServiceEntry
    group: networking.istio.io
    name: httpbin-ext
  rules:
  - backendRefs:
    - name: httpbin-egress-gateway-istio
      port: 80
---
# HTTPRoute to forward traffic from the egress gateway to httpbin.org
apiVersion: gateway.networking.k8s.io/v1
kind: HTTPRoute
metadata:
  name: forward-httpbin-from-egress-gateway
spec:
  parentRefs:
  - name: httpbin-egress-gateway
  hostnames:
  - httpbin.org
  rules:
  - backendRefs:
    - kind: Hostname
      group: networking.istio.io
      name: httpbin.org
      port: 80

# ServiceEntry to allow traffic to httpbin.org
apiVersion: networking.istio.io/v1
kind: ServiceEntry
metadata:
  name: httpbin-ext
spec:
  hosts:
  - httpbin.org
  ports:
  - number: 80
    name: http
    protocol: HTTP
  location: MESH_EXTERNAL
  resolution: DNS
---
# Gateway API Gateway for egress
apiVersion: gateway.networking.k8s.io/v1
kind: Gateway
metadata:
  name: httpbin-egress-gateway
  annotations:
    networking.istio.io/service-type: ClusterIP
spec:
  gatewayClassName: istio
  listeners:
  - name: http
    hostname: httpbin.org
    port: 80
    protocol: HTTP
    allowedRoutes:
      namespaces:
        from: Same
---
# HTTPRoute to direct traffic from sidecars to the egress gateway
apiVersion: gateway.networking.k8s.io/v1
kind: HTTPRoute
metadata:
  name: direct-httpbin-to-egress-gateway
spec:
  parentRefs:
  - kind: ServiceEntry
    group: networking.istio.io
    name: httpbin-ext
  rules:
  - backendRefs:
    - name: httpbin-egress-gateway-istio
      port: 80
---
# HTTPRoute to forward traffic from the egress gateway to httpbin.org
apiVersion: gateway.networking.k8s.io/v1
kind: HTTPRoute
metadata:
  name: forward-httpbin-from-egress-gateway
spec:
  parentRefs:
  - name: httpbin-egress-gateway
  hostnames:
  - httpbin.org
  rules:
  - backendRefs:
    - kind: Hostname
      group: networking.istio.io
      name: httpbin.org
      port: 80

Copy to Clipboard

Toggle word wrap

Apply the YAML file by running the following command:
```
oc apply -f egress-gateway-cr.yaml
```
```
$ oc apply -f egress-gateway-cr.yaml
```
Copy to Clipboard Toggle word wrap

Verification

Verify the status of the gateway configuration by running the following command:
```
oc describe gateway -n egress-gateway
```
```
$ oc describe gateway -n egress-gateway
```
Copy to Clipboard Toggle word wrap
Desired output is indicated by Programmed showing in the Status column.

Create a curl pod in the egress-gateway namespace by running the following command:

oc run test-pod --image=curlimages/curl:latest -n egress-gateway --rm -it --restart=Never -- sh

$ oc run test-pod --image=curlimages/curl:latest -n egress-gateway --rm -it --restart=Never -- sh

Copy to Clipboard

Toggle word wrap

By using the curl client, verify that you can access httpbin.org through the egress gateway by entering following command:
```
curl -v http://httpbin.org/get
```
```
$ curl -v http://httpbin.org/get
```
Copy to Clipboard Toggle word wrap
Desired output shows a response from httpbin.org that indicates egress traffic routes through the configured gateway.

3.4. Directing egress traffic through a gateway using the Kubernetes Gateway API in ambient mode
复制链接

Use the Kubernetes Gateway API and waypoint proxy to direct outbound HTTP traffic through an egress gateway.

Prerequisites

You have installed the OpenShift Service Mesh Operator version 3.2 or later.
You configured the Istio and IstioCNI resources with ambient profile.
You have created a Ztunnel resource.

Procedure

Optional: Enable the {k8} Gateway API custom resource definitions (CRDs).
Note
As of Kubernetes 1.28 and OpenShift Container Platform 4.18 or earlier version of Red Hat OpenShift Service Mesh, the Kubernetes Gateway API CRDs are not available by default and you must install the CRDs before you can use them. OpenShift Container Platform 4.19 and later versions install the CRDs by default.
Create a namespace called egress-gateway by running the following command:
```
oc create namespace egress-gateway
```
```
$ oc create namespace egress-gateway
```
Copy to Clipboard Toggle word wrap
Apply the ambient mode label to the namespace by running the following command:
```
oc label namespace egress-gateway istio.io/dataplane-mode=ambient
```
```
$ oc label namespace egress-gateway istio.io/dataplane-mode=ambient
```
Copy to Clipboard Toggle word wrap

Create a YAML file named egress-se.yaml that defines the ServiceEntry.

apiVersion: networking.istio.io/v1
kind: ServiceEntry
metadata:
  name: httpbin-ext
  namespace: egress-gateway
  labels:
    istio.io/use-waypoint: waypoint
spec:
  hosts:
  - httpbin.org
  ports:
  - number: 80
    name: http
    protocol: HTTP
  resolution: DNS

apiVersion: networking.istio.io/v1
kind: ServiceEntry
metadata:
  name: httpbin-ext
  namespace: egress-gateway
  labels:
    istio.io/use-waypoint: waypoint
spec:
  hosts:
  - httpbin.org
  ports:
  - number: 80
    name: http
    protocol: HTTP
  resolution: DNS

Copy to Clipboard

Toggle word wrap

Apply the YAML file by running the following command:
```
oc apply -f egress-se.yaml
```
```
$ oc apply -f egress-se.yaml
```
Copy to Clipboard Toggle word wrap

Create a YAML file named waypoint.yaml that creates a waypoint proxy in egress-gateway namespace similar to the following example:

apiVersion: gateway.networking.k8s.io/v1
kind: Gateway
metadata:
  name: waypoint
  namespace: egress-gateway
  labels:
    istio.io/gateway-for: service
spec:
  gatewayClassName: istio-waypoint
  listeners:
  - name: mesh
    port: 15008
    protocol: HBONE

apiVersion: gateway.networking.k8s.io/v1
kind: Gateway
metadata:
  name: waypoint
  namespace: egress-gateway
  labels:
    istio.io/gateway-for: service
spec:
  gatewayClassName: istio-waypoint
  listeners:
  - name: mesh
    port: 15008
    protocol: HBONE

Copy to Clipboard

Toggle word wrap

Apply the YAML file by running the following command:
```
oc apply -f waypoint.yaml
```
```
$ oc apply -f waypoint.yaml
```
Copy to Clipboard Toggle word wrap

Note

As an alternate to creating the waypoint.yaml YAML file, you can also set up waypoint proxy by running the following command:

istioctl waypoint apply --enroll-namespace --name waypoint --namespace egress-gateway

$ istioctl waypoint apply --enroll-namespace --name waypoint --namespace egress-gateway

Copy to Clipboard

Toggle word wrap

When you use the --enroll-namespace option, all services in the egress-gateway namespace (including ServiceEntries), will route their traffic through the waypoint.

Verification

Verify the status of the gateway configuration by running the following command:

oc get gateways.gateway.networking.k8s.io waypoint -n egress-gateway

$ oc get gateways.gateway.networking.k8s.io waypoint -n egress-gateway

Copy to Clipboard

Toggle word wrap

The PROGRAMMED column shows True when the configuration succeeds, similar to the following example:

NAME       CLASS            ADDRESS          PROGRAMMED   AGE
waypoint   istio-waypoint   172.30.227.148   True         9s

NAME       CLASS            ADDRESS          PROGRAMMED   AGE
waypoint   istio-waypoint   172.30.227.148   True         9s

Copy to Clipboard

Toggle word wrap

Create a curl pod in the egress-gateway namespace by running the following command:

oc run test-pod --image=curlimages/curl:latest -n egress-gateway --rm -it --restart=Never -- sh

$ oc run test-pod --image=curlimages/curl:latest -n egress-gateway --rm -it --restart=Never -- sh

Copy to Clipboard

Toggle word wrap

By using the curl client, verify that you can access httpbin.org through the egress gateway by running the following command:

curl -v http://httpbin.org/get

$ curl -v http://httpbin.org/get

Copy to Clipboard

Toggle word wrap

The output shows a response from httpbin.org service that indicates egress traffic routes through the configured gateway. The ztunnel logs should show traffic routed through the waypoint. The terminal should display information similar to the following output:

2025-10-24T08:08:35.242159Z info access connection complete src.addr=[fd01:0:0:5::b0]:56288 src.workload="test-pod" src.namespace="egress-gateway" src.identity="spiffe://cluster.local/ns/egress-gateway/sa/default" dst.addr=[fd01:0:0:5::af]:15008 dst.hbone_addr=[2001:2::2]:80 dst.service="httpbin.org" dst.workload="waypoint-5b668759d5-vrnx8" dst.namespace="egress-gateway" dst.identity="spiffe://cluster.local/ns/egress-gateway/sa/waypoint" direction="outbound" bytes_sent=78 bytes_recv=540 duration="957ms"

2025-10-24T08:08:35.242159Z info access connection complete src.addr=[fd01:0:0:5::b0]:56288 src.workload="test-pod" src.namespace="egress-gateway" src.identity="spiffe://cluster.local/ns/egress-gateway/sa/default" dst.addr=[fd01:0:0:5::af]:15008 dst.hbone_addr=[2001:2::2]:80 dst.service="httpbin.org" dst.workload="waypoint-5b668759d5-vrnx8" dst.namespace="egress-gateway" dst.identity="spiffe://cluster.local/ns/egress-gateway/sa/waypoint" direction="outbound" bytes_sent=78 bytes_recv=540 duration="957ms"

Copy to Clipboard

Toggle word wrap

此内容没有您所选择的语言版本。

Chapter 3. Directing outbound traffic through a gateway

3.1. About directing egress traffic through a gateway
复制链接

3.2. Directing egress traffic through a gateway using Istio APIs
复制链接

3.3. Directing egress traffic through a gateway by using the Kubernetes Gateway API
复制链接

3.4. Directing egress traffic through a gateway using the Kubernetes Gateway API in ambient mode
复制链接

学习

尝试、购买和销售

社区

关于红帽文档

让开源更具包容性

關於紅帽

Theme

Red Hat legal and privacy links

Red Hat legal and privacy links

此内容没有您所选择的语言版本。

Chapter 3. Directing outbound traffic through a gateway

3.1. About directing egress traffic through a gateway复制链接链接已复制到粘贴板!

3.2. Directing egress traffic through a gateway using Istio APIs复制链接链接已复制到粘贴板!

3.3. Directing egress traffic through a gateway by using the Kubernetes Gateway API复制链接链接已复制到粘贴板!

3.4. Directing egress traffic through a gateway using the Kubernetes Gateway API in ambient mode复制链接链接已复制到粘贴板!

学习

尝试、购买和销售

社区

关于红帽文档

让开源更具包容性

關於紅帽

Theme

Red Hat legal and privacy links

Red Hat legal and privacy links

3.1. About directing egress traffic through a gateway
复制链接

3.2. Directing egress traffic through a gateway using Istio APIs
复制链接

3.3. Directing egress traffic through a gateway by using the Kubernetes Gateway API
复制链接

3.4. Directing egress traffic through a gateway using the Kubernetes Gateway API in ambient mode
复制链接