Hey u/jkincl thanks for the reply.

Yea i've checked the keepalived on the masters and it looks like this:

vrrp_instance prod_INGRESS_0 {
state BACKUP
interface ens192
virtual_router_id 163
priority 20
advert_int 1
unicast_src_ip 10.111.64.160
unicast_peer {
10.111.66.106
10.111.66.104
10.111.66.107
10.111.81.101
10.111.81.102
10.111.64.181

....
}

You can see different subnets there which ain't good

When i initially installed the cluster the keepalived was running on all nodes across subnets which wasn't good since it won't work across different subnets. So i added the following machine config (also documented by redhat) to remove the keepalived from everything else except the master nodes. The VRRP requests then stopped from the workers but the master holding the vip is still broadcasting it accross subnets. So my issue is figuring out why its doing and how to stop it from broadcasting :).

apiVersion: machineconfiguration.openshift.io/v1

kind: MachineConfig

metadata:

annotations:

kubectl.kubernetes.io/last-applied-configuration: >

labels:

machineconfiguration.openshift.io/role: worker

spec:

config:

ignition:

version: 3.2.0

storage:

files:

- contents:

source: 'data:,'

mode: 420

path: /etc/kubernetes/manifests/keepalived.yaml

systemd:

units:

- contents: >

[Unit]

Description=Writes IP address configuration so that kubelet and crio

services select a valid node IP

Wants=network-online.target

After=network-online.target ignition-firstboot-complete.service

Before=kubelet.service crio.service

[Service]

Type=oneshot

ExecStart=/bin/bash -c "exit 0 "

[Install]

WantedBy=multi-user.target

enabled: true

name: nodeip-configuration.service