Skip to content

TELCODOCS-2273 - Remove Tech Preview Notifications #96701

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

Merged
merged 1 commit into from
Sep 2, 2025
Merged

TELCODOCS-2273 - Remove Tech Preview Notifications #96701

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
3 changes: 0 additions & 3 deletions modules/nw-metallb-bgppeer-cr.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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`
Expand Down
3 changes: 0 additions & 3 deletions modules/nw-metallb-example-bgppeer.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down Expand Up @@ -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]
Expand Down
6 changes: 0 additions & 6 deletions modules/nw-metallb-frr-k8s-configuration-crd.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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}"]
Expand Down Expand Up @@ -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
Expand Down Expand Up @@ -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`
Expand Down