-
Epic
-
Resolution: Unresolved
-
Major
-
None
-
None
-
None
-
Extend bgpcontroller to support multiple vrfs
-
8
-
False
-
-
False
-
Not Selected
-
Proposed
-
Proposed
-
To Do
-
Proposed
-
Proposed
-
-
-
Goal:
Right now the infra-operator does not support exposing pods to different vrfs.
We would need to change it so that different traffic can be advertised to different vrfs instead.
Acceptance Criteria:
Per network-attachment-definition advertisement, so that one can configure pods attached to a specific nad to be advertised to a certain vrf.
Example:
[zuul@controller-0 ~]$ oc get bgpconfiguration bgpconfiguration-vrf1 -o yaml apiVersion: network.openstack.org/v1beta1 kind: BGPConfiguration metadata: name: bgpconfiguration-vrf1 namespace: openstack spec: frrConfigurationNamespace: metallb-system networkAttachmentDefinitions: - internalapi - ctlplane - storage routerASNs: - 64999
[zuul@controller-0 ~]$ oc get bgpconfiguration bgpconfiguration-vrf2 -o yaml apiVersion: network.openstack.org/v1beta1 kind: BGPConfiguration metadata: name: bgpconfiguration-vrf2 namespace: openstack spec: frrConfigurationNamespace: metallb-system networkAttachmentDefinitions: - tenant routerASNs: - 100
