Skip to content

Commit 0a75b02

Browse files
committed
OSDOCS-4767: Add Kuryr deprecation notices
* Add dep mod to to Kuryr-based installation assemblies * Add dep snippet to some Kuryr mods
1 parent 24262de commit 0a75b02

6 files changed

+18
-0
lines changed

installing/installing_openstack/installing-openstack-installer-kuryr.adoc

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -6,6 +6,9 @@ include::_attributes/common-attributes.adoc[]
66

77
toc::[]
88

9+
:FeatureName: Kuryr
10+
include::modules/deprecated-feature.adoc[leveloffset=+1]
11+
912
In {product-title} version {product-version}, you can install a customized cluster on
1013
{rh-openstack-first} that uses Kuryr SDN. To customize the installation, modify parameters in the `install-config.yaml` before you install the cluster.
1114

installing/installing_openstack/installing-openstack-user-kuryr.adoc

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -6,6 +6,9 @@ include::_attributes/common-attributes.adoc[]
66

77
toc::[]
88

9+
:FeatureName: Kuryr
10+
include::modules/deprecated-feature.adoc[leveloffset=+1]
11+
912
In {product-title} version {product-version}, you can install a cluster on
1013
{rh-openstack-first} that runs on user-provisioned infrastructure.
1114

modules/installation-osp-about-kuryr.adoc

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -6,6 +6,9 @@
66
[id="installation-osp-about-kuryr_{context}"]
77
= About Kuryr SDN
88

9+
:FeatureName: Kuryr
10+
include::snippets/deprecated-feature.adoc[]
11+
912
link:https://docs.openstack.org/kuryr-kubernetes/latest/[Kuryr] is a container
1013
network interface (CNI) plug-in solution that uses the
1114
link:https://docs.openstack.org/neutron/latest/[Neutron] and

modules/installation-osp-kuryr-api-scaling.adoc

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -6,6 +6,9 @@
66
[id="installation-osp-kuryr-api-scaling_{context}"]
77
= Scaling clusters that use Kuryr by using Octavia
88

9+
:FeatureName: Kuryr
10+
include::snippets/deprecated-feature.adoc[]
11+
912
If your cluster uses Kuryr, associate the API floating IP address of your cluster with the pre-existing Octavia load balancer.
1013

1114
.Prerequisites

modules/installation-osp-kuryr-ingress-scaling.adoc

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -6,6 +6,9 @@
66
[id="installation-osp-kuryr-octavia-scale_{context}"]
77
= Scaling for ingress traffic by using {rh-openstack} Octavia
88

9+
:FeatureName: Kuryr
10+
include::snippets/deprecated-feature.adoc[]
11+
912
You can use Octavia load balancers to scale Ingress controllers on clusters that use Kuryr.
1013

1114
.Prerequisites

modules/installation-osp-kuryr-octavia-upgrade.adoc

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -6,6 +6,9 @@
66
[id="installation-osp-kuryr-octavia-configure_{context}"]
77
= Using the Octavia OVN load balancer provider driver with Kuryr SDN
88

9+
:FeatureName: Kuryr
10+
include::snippets/deprecated-feature.adoc[]
11+
912
If your {product-title} cluster uses Kuryr and was installed on a {rh-openstack-first} 13 cloud
1013
that was later upgraded to {rh-openstack} 16, you can configure it to use the Octavia OVN provider driver.
1114

0 commit comments

Comments
 (0)