Adds constraint note to egressIP object example yaml

[stevsmit]

trafficstars

Version(s): 4.12+

Issue: https://issues.redhat.com/browse/OCPBUGS-36497

Link to docs preview: https://78423--ocpdocs-pr.netlify.app/openshift-enterprise/latest/networking/ovn_kubernetes_network_provider/configuring-egress-ips-ovn.html#nw-egress-ips-object_configuring-egress-ips-ovn

QE review:

• [ ] QE has approved this change.

Additional information:

[ocpdocs-previewbot]

🤖 Wed Jul 03 14:04:49 - Prow CI generated the docs preview:

https://78423--ocpdocs-pr.netlify.app/openshift-enterprise/latest/networking/ovn_kubernetes_network_provider/configuring-egress-ips-ovn.html https://78423--ocpdocs-pr.netlify.app/openshift-rosa/latest/networking/ovn_kubernetes_network_provider/configuring-egress-ips-ovn.html

[openshift-ci[bot]]

@stevsmit: all tests passed!

Full PR test history. Your PR dashboard.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

[huiran0826]

/lgtm

[martinkennelly]

/hold

There is a user story this can block that needs to be understood - in dual stack, if a CU wants to have Egress IP for both ipv4 and ipv6 for a pod, with this constraint, and with the existing constraint that only one EIP object can select a pod, they are blocked.