Description of problem:
ingress ip should not be assigned by ingress controller for cloud vm cluster. since it should be configure the cloud-specific load balancers
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Set 'ingressIPNetworkCIDR: 172.31.0.0/16' in master-config.yaml
2. Restart the master service
3. Create one 'LoadBalancer' type service
4. oc get svc
the ingress ip was assigned
# oc get svc ws-unsecure -o yaml
- name: http
- ip: 172.31.4.231
ingress ip should not be assigned for cloud vm cluster.
This is a known problem and a fix is in process.
This has been merged into ose and is in OSE v22.214.171.124 or newer.
verified this bug on
When given an ingressIPNetworkCIDR option on master-config.yaml. the master service will cannot be started.
and check the log from journalctl -xe:
networkConfig.ingressIPNetworkCIDR: Invalid value: "10.66.0.0/16": should not be provided when a cloud-provider is enabled
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.