From 4a0320c05ba5e2b53df026dc1826725c201fdc81 Mon Sep 17 00:00:00 2001 From: Shane Lovern Date: Fri, 25 Jul 2025 15:46:39 +0100 Subject: [PATCH] TELCODOCS-2273 - Remove Tech Preview Notifications --- modules/nw-metallb-bgppeer-cr.adoc | 3 --- modules/nw-metallb-example-bgppeer.adoc | 3 --- modules/nw-metallb-frr-k8s-configuration-crd.adoc | 6 ------ 3 files changed, 12 deletions(-) diff --git a/modules/nw-metallb-bgppeer-cr.adoc b/modules/nw-metallb-bgppeer-cr.adoc index fdc9f06297d1..3e31bc06ed21 100644 --- a/modules/nw-metallb-bgppeer-cr.adoc +++ b/modules/nw-metallb-bgppeer-cr.adoc @@ -55,9 +55,6 @@ You must establish a point-to-point, layer 2 connection between the two BGP peer You can use unnumbered BGP peering with IPv4, IPv6, or dual-stack, but you must enable IPv6 RAs (Router Advertisements). Each interface is limited to one BGP connection. If you use this field, you cannot specify a value in the `spec.peerAddress` field. -The `spec.bgp.routers.neighbors.interface` field is a Technology Preview feature only. -For more information about the support scope of Red{nbsp}Hat Technology Preview features, see link:https://access.redhat.com/support/offerings/techpreview/[Technology Preview Features Support Scope]. - |`spec.sourceAddress` |`string` diff --git a/modules/nw-metallb-example-bgppeer.adoc b/modules/nw-metallb-example-bgppeer.adoc index 3a46ac7142bb..af5c8fd28d24 100644 --- a/modules/nw-metallb-example-bgppeer.adoc +++ b/modules/nw-metallb-example-bgppeer.adoc @@ -5,7 +5,6 @@ :_mod-docs-content-type: PROCEDURE [id="nw-metallb-example-bgppeer_{context}"] = Example BGP peer configurations -:FeatureName: The `spec.interface` field [id="nw-metallb-example-limit-nodes-bgppeer_{context}"] == Example: Limit which nodes connect to a BGP peer @@ -87,8 +86,6 @@ spec: [id="nw-metallb-example-unnumbered-bgp-peering_{context}"] == Example: Specify BGP peers for unnumbered BGP peering -include::snippets/technology-preview.adoc[] - To configure unnumbered BGP peering, specify the interface in the `spec.interface` field by using the following example configuration: [source,yaml] diff --git a/modules/nw-metallb-frr-k8s-configuration-crd.adoc b/modules/nw-metallb-frr-k8s-configuration-crd.adoc index e293a17090e9..98b90e03658e 100644 --- a/modules/nw-metallb-frr-k8s-configuration-crd.adoc +++ b/modules/nw-metallb-frr-k8s-configuration-crd.adoc @@ -6,8 +6,6 @@ [id="nw-metallb-frrconfiguration-crd_{context}"] = Configuring the FRRConfiguration CRD -:FeatureName: The `spec.bgp.routers.neighbors.interface` field - The following section provides reference examples that use the `FRRConfiguration` custom resource (CR). [id="nw-metallb-frrconfiguration-crd-routers_{context}"] @@ -213,8 +211,6 @@ spec: [id="nw-metallb-frrconfiguration-crd-interface_{context}"] == The interface field -include::snippets/technology-preview.adoc[] - You can use the `interface` field to configure unnumbered BGP peering by using the following example configuration: .Example `FRRConfiguration` CR @@ -314,8 +310,6 @@ Use this field to configure unnumbered BGP peering. There must be a point-to-point, layer 2 connection between the two BGP peers. You can use unnumbered BGP peering with IPv4, IPv6, or dual-stack, but you must enable IPv6 RAs (Router Advertisements). Each interface is limited to one BGP connection. -The `spec.bgp.routers.neighbors.interface` field is a Technology Preview feature only. -For more information about the support scope of Red{nbsp}Hat Technology Preview features, see link:https://access.redhat.com/support/offerings/techpreview/[Technology Preview Features Support Scope]. |`spec.bgp.routers.neighbors.port` |`integer`