Epic Goal

As an administrator for OpenShift on vSphere using the IPI installation workflow, I need Keepalived configured with unicast instead of multicast.

Why is this important?

OCP IPI on vSphere IPI configures keepalived in multicast mode, which can lead to VRRP ID clashes if multiple clusters with similar cluster name are deployed on the same L2 network. This has been fixed on OCP IPI on bare metal, but not on vSphere IPI.

Previous Work

Add support for Keepalived mode update:
https://github.com/openshift/baremetal-runtimecfg/pull/75

[vsphere][spike] Will unicast keepalived work?

https://issues.redhat.com/browse/SPLAT-149

https://github.com/openshift/baremetal-runtimecfg/blob/8d4eecc8b3748a19506a6ad59ef551afcacfa6f5/pkg/config/node.go#L73

Done Checklist

• CI - CI is running, tests are automated and merged.
• Release Enablement <link to Feature Enablement Presentation>
• DEV - Upstream code and tests merged: <link to meaningful PR or GitHub Issue>
• DEV - Upstream documentation merged: <link to meaningful PR or GitHub Issue>
• DEV - Downstream build attached to advisory: <link to errata>
• QE - Test plans in Polarion: <link or reference to Polarion>
• QE - Automated tests merged: <link or reference to automated tests>
• DOC - Downstream documentation merged: <link to meaningful PR>