-
Bug
-
Resolution: Unresolved
-
Major
-
rhos-18.0.11
-
None
-
5
-
False
-
-
False
-
?
-
None
-
-
-
-
Sprint 7
-
1
-
Important
When RHOSO is configured with BGP at controlplane (a CR with BGPConfiguration is applied), if octavia has been enabled, the IPs that can be found on the octavia-hmport-map configmap have to be exposed.
The is needed for the amphora VMs to connect to the healthmonitor pods.
[zuul@controller-0 kustomize_deploy]$ oc get configmaps octavia-hmport-map -o jsonpath={.data}; echo {"hm_worker-0":"172.23.0.103","hm_worker-1":"172.23.0.105","hm_worker-2":"172.23.0.107","rsyslog_worker-0":"172.23.0.104","rsyslog_worker-1":"172.23.0.106","rsyslog_worker-2":"172.23.0.108"}
Same applies to designate, using two configmaps:
oc get cm designate-bind-ip-map -o yaml
apiVersion: v1
data:
bind_address_0: 172.67.0.100
bind_address_1: 172.67.0.101
bind_address_2: 172.67.0.102
$ oc get cm designate-mdns-ip-map -o yaml
apiVersion: v1
data:
mdns_address_0: 172.67.0.97
mdns_address_1: 172.67.0.98
mdns_address_2: 172.67.0.99
- is depended on by
-
OSPRH-13720 BGP+Octavia with amphora
-
- In Progress
-
- links to