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
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.
You can assign one or more egress IP addresses to a namespace or to specific pods in a namespace.
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.
Create an EgressIP
object:
Create a <egressips_name>.yaml
file where <egressips_name>
is the name of the object.
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
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. |
egressips.k8s.ovn.org/<egressips_name> created
Optional: Save the <egressips_name>.yaml
file so that you can make changes later.
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. |