-
Bug
-
Resolution: Won't Do
-
Undefined
-
None
-
4.16.0
-
None
-
Important
-
Yes
-
Rejected
-
False
-
Description of problem:
this is NOT about ELB scenario
when api/ingress vip using internal LB (keepliaved) is out machineNetworkCIDR on vsphere. Network operator will show error Error while synchronizing spec and status of infrastructures.config.openshift.io/cluster: Error on validating API VIPs and Machine Networks: VIP '10.185.104.100' cannot be found in any machine network"
Version-Release number of selected component (if applicable):
4.16.0-0.nightly-2024-06-14-130320
How reproducible:
always
Steps to Reproduce:
1. setup cluster on vsphere which api/ingress is out of machineCIDR networking: clusterNetwork: - cidr: 10.128.0.0/14 hostPrefix: 23 machineNetwork: - cidr: 10.184.15.128/25 networkType: OVNKubernetes serviceNetwork: - 172.30.0.0/16 platform: vsphere: apiVIPs: - 10.185.104.100 ingressVIPs: - 10.185.104.101 2. 3.
Actual results:
network operator report error: Error while synchronizing spec and status of infrastructures.config.openshift.io/cluster: Error on validating API VIPs and Machine Networks: VIP '10.185.104.100' cannot be found in any machine network"
Expected results:
no errors
Additional info: