Skip to content

Commit f80cebb

Browse files
authored
Merge pull request #96701 from slovern/TELCODOCS-2273
TELCODOCS-2273 - Remove Tech Preview Notifications
2 parents 170f94b + 4a0320c commit f80cebb

File tree

3 files changed

+0
-12
lines changed

3 files changed

+0
-12
lines changed

modules/nw-metallb-bgppeer-cr.adoc

Lines changed: 0 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -55,9 +55,6 @@ You must establish a point-to-point, layer 2 connection between the two BGP peer
5555
You can use unnumbered BGP peering with IPv4, IPv6, or dual-stack, but you must enable IPv6 RAs (Router Advertisements).
5656
Each interface is limited to one BGP connection.
5757
If you use this field, you cannot specify a value in the `spec.peerAddress` field.
58-
The `spec.bgp.routers.neighbors.interface` field is a Technology Preview feature only.
59-
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].
60-
6158

6259
|`spec.sourceAddress`
6360
|`string`

modules/nw-metallb-example-bgppeer.adoc

Lines changed: 0 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,6 @@
55
:_mod-docs-content-type: PROCEDURE
66
[id="nw-metallb-example-bgppeer_{context}"]
77
= Example BGP peer configurations
8-
:FeatureName: The `spec.interface` field
98

109
[id="nw-metallb-example-limit-nodes-bgppeer_{context}"]
1110
== Example: Limit which nodes connect to a BGP peer
@@ -87,8 +86,6 @@ spec:
8786
[id="nw-metallb-example-unnumbered-bgp-peering_{context}"]
8887
== Example: Specify BGP peers for unnumbered BGP peering
8988

90-
include::snippets/technology-preview.adoc[]
91-
9289
To configure unnumbered BGP peering, specify the interface in the `spec.interface` field by using the following example configuration:
9390

9491
[source,yaml]

modules/nw-metallb-frr-k8s-configuration-crd.adoc

Lines changed: 0 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -6,8 +6,6 @@
66
[id="nw-metallb-frrconfiguration-crd_{context}"]
77
= Configuring the FRRConfiguration CRD
88

9-
:FeatureName: The `spec.bgp.routers.neighbors.interface` field
10-
119
The following section provides reference examples that use the `FRRConfiguration` custom resource (CR).
1210

1311
[id="nw-metallb-frrconfiguration-crd-routers_{context}"]
@@ -213,8 +211,6 @@ spec:
213211
[id="nw-metallb-frrconfiguration-crd-interface_{context}"]
214212
== The interface field
215213

216-
include::snippets/technology-preview.adoc[]
217-
218214
You can use the `interface` field to configure unnumbered BGP peering by using the following example configuration:
219215

220216
.Example `FRRConfiguration` CR
@@ -314,8 +310,6 @@ Use this field to configure unnumbered BGP peering.
314310
There must be a point-to-point, layer 2 connection between the two BGP peers.
315311
You can use unnumbered BGP peering with IPv4, IPv6, or dual-stack, but you must enable IPv6 RAs (Router Advertisements).
316312
Each interface is limited to one BGP connection.
317-
The `spec.bgp.routers.neighbors.interface` field is a Technology Preview feature only.
318-
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].
319313

320314
|`spec.bgp.routers.neighbors.port`
321315
|`integer`

0 commit comments

Comments
 (0)