From c56b49d22f40d2c897dfff122ac024213c99a39c Mon Sep 17 00:00:00 2001 From: Jason Boxman Date: Mon, 6 Jan 2025 15:16:38 -0500 Subject: [PATCH 1/2] Add release note for BGP routing - https://issues.redhat.com/browse/OSDOCS-10810 --- release_notes/ocp-4-18-release-notes.adoc | 48 +++++++++++++++++++++++ 1 file changed, 48 insertions(+) diff --git a/release_notes/ocp-4-18-release-notes.adoc b/release_notes/ocp-4-18-release-notes.adoc index d3ac51e8ff29..842d79f2009e 100644 --- a/release_notes/ocp-4-18-release-notes.adoc +++ b/release_notes/ocp-4-18-release-notes.adoc @@ -852,6 +852,54 @@ 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 utilize 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} with the Metal LB Operator deployed, 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` 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 execute the migration, run the following command: ++ +[source,terminal] +---- +$ bash migrate.sh +---- + +. To confirm that the migration succeeded, run 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 xref:../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. From 3f6084b54a60f58dfff77278cf0fa8deaf1967ac Mon Sep 17 00:00:00 2001 From: Jason Boxman Date: Thu, 15 May 2025 13:38:51 -0400 Subject: [PATCH 2/2] Fixup --- release_notes/ocp-4-18-release-notes.adoc | 16 +++++++--------- 1 file changed, 7 insertions(+), 9 deletions(-) diff --git a/release_notes/ocp-4-18-release-notes.adoc b/release_notes/ocp-4-18-release-notes.adoc index 842d79f2009e..b5cc91874487 100644 --- a/release_notes/ocp-4-18-release-notes.adoc +++ b/release_notes/ocp-4-18-release-notes.adoc @@ -855,9 +855,9 @@ For more information, see xref:../networking/multiple_networks/secondary_network [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 utilize multi-homing, link redundancy, and fast convergence. BGP configuration is managed with the `FRRConfiguration` custom resource (CR). +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} with the Metal LB Operator deployed, 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: +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: + @@ -866,39 +866,37 @@ When upgrading from an earlier version of {product-title} with the Metal LB Oper $ oc create namespace openshift-frr-k8s ---- -. To automate the migration, create a `migrate.sh` with the following content: +. 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 execute the migration, run the following command: +. To run the migration script, enter the following command: + [source,terminal] ---- $ bash migrate.sh ---- -. To confirm that the migration succeeded, run the following command: +. 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. +After the migration is complete, you can remove the `FRR-K8s` custom resources from the `metallb-system` namespace. -For more information, see xref:../networking/bgp_routing/about-bgp-routing.adoc#about-bgp-routing[About BGP routing]. +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