Skip to content

[enterprise-4.18] Add release note for BGP routing #88842

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 2 commits into
base: enterprise-4.18
Choose a base branch
from
Open

[enterprise-4.18] Add release note for BGP routing #88842

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
c56b49d
Add release note for BGP routing
jab-rh Jan 6, 2025
3f6084b
Fixup
jab-rh May 15, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
46 changes: 46 additions & 0 deletions release_notes/ocp-4-18-release-notes.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -852,6 +852,52 @@ With this release, you can configure a multi-network policy for the following ne

For more information, see xref:../networking/multiple_networks/secondary_networks/configuring-multi-network-policy.adoc[Configuring multi-network policy]

[id="ocp-4-18-support-for-bgp-routing-protocol_{context}"]
==== Support for the BGP routing protocol

The Cluster Network Operator (CNO) now supports enabling Border Gateway Protocol (BGP) routing. With BGP, you can import and export routes to the underlying provider network and use multi-homing, link redundancy, and fast convergence. BGP configuration is managed with the `FRRConfiguration` custom resource (CR).

When upgrading from an earlier version of {product-title} in which you installed the MetalLB Operator, you must manually migrate your custom frr-k8s configurations from the `metallb-system` namespace to the `openshift-frr-k8s` namespace. To move these CRs, enter the following commands:

. To create the `openshift-frr-k8s` namespace, enter the following command:
+
[source,terminal]
----
$ oc create namespace openshift-frr-k8s
----

. To automate the migration, create a `migrate.sh` file with the following content:
+
[source,bash]
----
#!/bin/bash
OLD_NAMESPACE="metallb-system"
NEW_NAMESPACE="openshift-frr-k8s"
FILTER_OUT="metallb-"
oc get frrconfigurations.frrk8s.metallb.io -n "${OLD_NAMESPACE}" -o json |\
jq -r '.items[] | select(.metadata.name | test("'"${FILTER_OUT}"'") | not)' |\
jq -r '.metadata.namespace = "'"${NEW_NAMESPACE}"'"' |\
oc create -f -
----

. To run the migration script, enter the following command:
+
[source,terminal]
----
$ bash migrate.sh
----

. To verify that the migration succeeded, enter the following command:
+
[source,terminal]
----
$ oc get frrconfigurations.frrk8s.metallb.io -n openshift-frr-k8s
----

After the migration is complete, you can remove the `FRR-K8s` custom resources from the `metallb-system` namespace.

For more information, see x!ref:../networking/bgp_routing/about-bgp-routing.adoc#about-bgp-routing[About BGP routing].

[id="ocp-release-notes-networking-whitelist-blacklist-annotation-updated-allowlist-denylist_{context}"]
==== Updated terminology for whitelist and blacklist annotations
The terminology for the `ip_whitelist` and `ip_blacklist` annotations have been updated to `ip_allowlist` and `ip_denylist`, respectively. Currently, {product-title} still supports the `ip_whitelist` and `ip_blacklist` annotations. However, these annotations are planned for removal in a future release.
Expand Down