Use predictableIPs labels to advertise pods addresses #487
+259
−57
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Octavia and Designate have special configmaps storing ip addresses that are internally managed.
$ oc get configmaps octavia-hmport-map -o yaml
apiVersion: v1
data:
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
kind: ConfigMap
metadata:
name: octavia-hmport-map
namespace: openstack
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
These IPs should also be advertised in addition to the network-attachment-definitions for each pod.
This change watches pods for the presence of a predictableip label, if this is found it appends the ip to the already-existing frrconfiguration created for the network-attachment-definition ip.
Jira: https://issues.redhat.com/browse/OSPRH-20083
Assisted-by: claude-4.5-sonnet