This is a cache of https://docs.openshift.com/container-platform/4.9/networking/ovn_kubernetes_network_provider/assigning-egress-ips-ovn.html. It is a snapshot of the page at 2024-11-20T18:13:48.985+0000.
Assigning an <strong>egress</strong> IP address - OVN-Kubernetes default CNI network provider | Networking | OpenShift Container Platform 4.9
    Soon, all Red Hat OpenShift documentation will only be available on docs.redhat.com, the official location of all Red Hat product documentation. Get familiar with the updated experience today!
  1. Documentation
    2. history
×

Assigning an egress IP address

As a cluster administrator, you can assign an egress IP address for traffic leaving the cluster from a namespace or from specific pods in a namespace.

Assigning an egress IP address to a namespace

You can assign one or more egress IP addresses to a namespace or to specific pods in a namespace.

Prerequisites

  • Install the OpenShift CLI (oc).

  • Log in to the cluster as a cluster administrator.

  • Configure at least one node to host an egress IP address.

Procedure

  1. Create an egressIP object:

    1. Create a <egressips_name>.yaml file where <egressips_name> is the name of the object.

    2. In the file that you created, define an egressIP object, as in the following example:

      apiVersion: k8s.ovn.org/v1
kind: egressIP
metadata:
  name: egress-project1
spec:
  egressIPs:
  - 192.168.127.10
  - 192.168.127.11
  namespaceSelector:
    matchLabels:
      env: qa

  2. To create the object, enter the following command.

    $ oc apply -f <egressips_name>.yaml (1)
    1 Replace <egressips_name> with the name of the object.
    Example output
    egressips.k8s.ovn.org/<egressips_name> created

  3. Optional: Save the <egressips_name>.yaml file so that you can make changes later.

  4. Add labels to the namespace that requires egress IP addresses. To add a label to the namespace of an egressIP object defined in step 1, run the following command:

    $ oc label ns <namespace> env=qa (1)
    1 Replace <namespace> with the namespace that requires egress IP addresses.

Additional resources