openshift · kalexand-rh · Feb 4, 2022 · Nov 23, 2021
diff --git a/administering_a_cluster/snippets b/administering_a_cluster/snippets
@@ -0,0 +1 @@
+../snippets
diff --git a/applications/application_life_cycle_management/snippets b/applications/application_life_cycle_management/snippets
@@ -0,0 +1 @@
+../snippets
diff --git a/applications/snippets b/applications/snippets
@@ -0,0 +1 @@
+../snippets
diff --git a/architecture/snippets b/architecture/snippets
@@ -0,0 +1 @@
+../snippets
diff --git a/authentication/snippets b/authentication/snippets
@@ -0,0 +1 @@
+../snippets
diff --git a/...cation_backup_and_restore/backing_up_and_restoring/backing-up-applications.adoc b/...cation_backup_and_restore/backing_up_and_restoring/backing-up-applications.adoc
@@ -11,7 +11,7 @@ You back up applications by creating a xref:../../../backup_and_restore/applicat
 The `Backup` CR creates backup files for Kubernetes resources and internal images, on S3 object storage, and snapshots for persistent volumes (PVs), if the cloud provider uses a native snapshot API or the xref:../../../backup_and_restore/application_backup_and_restore/backing_up_and_restoring/backing-up-applications.adoc#oadp-backing-up-pvs-csi_backing-up-applications[Container Storage Interface (CSI)] to create snapshots, such as OpenShift Container Storage 4. For more information, see xref:../../../storage/container_storage_interface/persistent-storage-csi-snapshots.adoc#persistent-storage-csi-snapshots[CSI volume snapshots].
 
 :FeatureName: The `CloudStorage` API for S3 storage
-include::modules/technology-preview.adoc[]
+include::snippets/technology-preview.adoc[]
 
 If your cloud provider has a native snapshot API or supports xref:../../../backup_and_restore/application_backup_and_restore/backing_up_and_restoring/backing-up-applications.adoc#oadp-backing-up-pvs-csi_backing-up-applications[Container Storage Interface (CSI) snapshots], the `Backup` CR backs up persistent volumes by creating snapshots. For more information, see the xref:../../../storage/container_storage_interface/persistent-storage-csi-snapshots.adoc#persistent-storage-csi-snapshots-overview_persistent-storage-csi-snapshots[Overview of CSI volume snapshots] in the {product-title} documentation.
 

diff --git a/backup_and_restore/application_backup_and_restore/backing_up_and_restoring/snippets b/backup_and_restore/application_backup_and_restore/backing_up_and_restoring/snippets
@@ -0,0 +1 @@
+../../../snippets/
diff --git a/...nd_restore/application_backup_and_restore/installing/about-installing-oadp.adoc b/...nd_restore/application_backup_and_restore/installing/about-installing-oadp.adoc
@@ -17,7 +17,7 @@ To back up Kubernetes resources and internal images, you must have object storag
 * S3-compatible object storage, such as Noobaa or Minio
 
 :FeatureName: The `CloudStorage` API for S3 storage
-include::modules/technology-preview.adoc[]
+include::snippets/technology-preview.adoc[]
 
 You can back up persistent volumes (PVs) by using snapshots or Restic.
 

diff --git a/..._and_restore/application_backup_and_restore/installing/installing-oadp-aws.adoc b/..._and_restore/application_backup_and_restore/installing/installing-oadp-aws.adoc
@@ -12,7 +12,7 @@ toc::[]
 You install the Openshift API for Data Protection (OADP) with Amazon Web Services (AWS) by installing the OADP Operator, configuring AWS for Velero, and then installing the Data Protection Application.
 
 :FeatureName: The `CloudStorage` API for S3 storage
-include::modules/technology-preview.adoc[]
+include::snippets/technology-preview.adoc[]
 
 To install the OADP Operator in a restricted network environment, you must first disable the default OperatorHub sources and mirror the Operator catalog. See xref:../../../operators/admin/olm-restricted-networks.adoc#olm-restricted-networks[Using Operator Lifecycle Manager on restricted networks] for details.
 

diff --git a/...nd_restore/application_backup_and_restore/installing/installing-oadp-azure.adoc b/...nd_restore/application_backup_and_restore/installing/installing-oadp-azure.adoc
@@ -12,7 +12,7 @@ toc::[]
 You install the Openshift API for Data Protection (OADP) with Microsoft Azure by installing the OADP Operator, configuring Azure for Velero, and then installing the Data Protection Application.
 
 :FeatureName: The `CloudStorage` API for S3 storage
-include::modules/technology-preview.adoc[]
+include::snippets/technology-preview.adoc[]
 
 To install the OADP Operator in a restricted network environment, you must first disable the default OperatorHub sources and mirror the Operator catalog. See xref:../../../operators/admin/olm-restricted-networks.adoc#olm-restricted-networks[Using Operator Lifecycle Manager on restricted networks] for details.
 

diff --git a/..._and_restore/application_backup_and_restore/installing/installing-oadp-gcp.adoc b/..._and_restore/application_backup_and_restore/installing/installing-oadp-gcp.adoc
@@ -12,7 +12,7 @@ toc::[]
 You install the Openshift API for Data Protection (OADP) with Google Cloud Platform (GCP) by installing the OADP Operator, configuring GCP for Velero, and then installing the Data Protection Application.
 
 :FeatureName: The `CloudStorage` API for S3 storage
-include::modules/technology-preview.adoc[]
+include::snippets/technology-preview.adoc[]
 
 To install the OADP Operator in a restricted network environment, you must first disable the default OperatorHub sources and mirror the Operator catalog. See xref:../../../operators/admin/olm-restricted-networks.adoc#olm-restricted-networks[Using Operator Lifecycle Manager on restricted networks] for details.
 

diff --git a/..._and_restore/application_backup_and_restore/installing/installing-oadp-mcg.adoc b/..._and_restore/application_backup_and_restore/installing/installing-oadp-mcg.adoc
@@ -14,7 +14,7 @@ You install the Openshift API for Data Protection (OADP) with Multicloud Object
 MCG is a component of OpenShift Container Storage (OCS). You configure MCG as a backup location in the `DataProtectionApplication` custom resource (CR).
 
 :FeatureName: The `CloudStorage` API for S3 storage
-include::modules/technology-preview.adoc[]
+include::snippets/technology-preview.adoc[]
 
 If your cloud provider has a native snapshot API, configure a snapshot location. If your cloud provider does not support snapshots or if your storage is NFS, you can create backups with Restic.
 

diff --git a/..._and_restore/application_backup_and_restore/installing/installing-oadp-ocs.adoc b/..._and_restore/application_backup_and_restore/installing/installing-oadp-ocs.adoc
@@ -14,7 +14,7 @@ You install the Openshift API for Data Protection (OADP) with OpenShift Containe
 You can configure xref:../../../backup_and_restore/application_backup_and_restore/installing/installing-oadp-mcg.adoc#installing-oadp-mcg[Multicloud Object Gateway] or any S3-compatible object storage as a backup location in the `DataProtectionApplication` custom resource (CR).
 
 :FeatureName: The `CloudStorage` API for S3 storage
-include::modules/technology-preview.adoc[]
+include::snippets/technology-preview.adoc[]
 
 If the cloud provider has a native snapshot API, you can configure cloud storage as a snapshot location in the `DataProtectionApplication` CR. You do not need to specify a snapshot location for Restic or Container Storage Interface (CSI) snapshots.
 

diff --git a/backup_and_restore/application_backup_and_restore/installing/snippets b/backup_and_restore/application_backup_and_restore/installing/snippets
@@ -0,0 +1 @@
+../../../snippets/
diff --git a/backup_and_restore/application_backup_and_restore/snippets b/backup_and_restore/application_backup_and_restore/snippets
@@ -0,0 +1 @@
+../../snippets/
diff --git a/backup_and_restore/index.adoc b/backup_and_restore/index.adoc
@@ -52,7 +52,7 @@ You can always recover from a disaster situation by xref:../backup_and_restore/c
 // ** S3-compatible object storage, such as Noobaa or Minio
 //
 // :FeatureName: The `CloudStorage` API for S3 storage
-// include::modules/technology-preview.adoc[]
+// include::snippets/technology-preview.adoc[]
 //
 // * To back up PVs with snapshots, you must have cloud storage that has a native snapshot API or supports Container Storage Interface (CSI) snapshots, such as the following providers:
 //

diff --git a/backup_and_restore/snippets b/backup_and_restore/snippets
@@ -0,0 +1 @@
+../snippets
diff --git a/cicd/snippets b/cicd/snippets
@@ -0,0 +1 @@
+../snippets
diff --git a/cli_reference/helm_cli/snippets b/cli_reference/helm_cli/snippets
@@ -0,0 +1 @@
+../snippets
diff --git a/cli_reference/snippets b/cli_reference/snippets
@@ -0,0 +1 @@
+../snippets
diff --git a/cloud_infrastructure_access/snippets b/cloud_infrastructure_access/snippets
@@ -0,0 +1 @@
+../snippets
diff --git a/cloud_providers/snippets b/cloud_providers/snippets
@@ -0,0 +1 @@
+../snippets/
diff --git a/contributing_to_docs/doc_guidelines.adoc b/contributing_to_docs/doc_guidelines.adoc
@@ -374,8 +374,14 @@ You must use the .adoc extension in order for the link to work correctly and you
 == Indicating Technology Preview Features
 
 To indicate that a feature is in Technology Preview, include the
-`modules/technology-preview.adoc` file in the feature's assembly to keep the
-supportablity wording consistent across Technology Preview features and provide a value for thee :FeatureName: variable before you include this module.
+`snippets/technology-preview.adoc` file in the feature's assembly to keep the
+supportability wording consistent across Technology Preview features and provide a value for the :FeatureName: variable before you include this module.
+
+See link:https://github.com/openshift/openshift-docs/pull/13878/files#diff-615ba1bf3b09d11a9c2604b775aa32f2[an example] of how this is applied.
+
+== Indicating deprecated features
+
+To indicate that a feature is deprecated, include the `modules/deprecated-feature.adoc` file in the feature's assembly, or to each relevant assembly such as for a deprecated Operator, to keep the supportability wording consistent across deprecated features. Provide a value for the :FeatureName: variable before you include this module.
 
 See
 link:https://github.com/openshift/openshift-docs/pull/13878/files#diff-615ba1bf3b09d11a9c2604b775aa32f2[an

diff --git a/contributing_to_docs/snippets b/contributing_to_docs/snippets
@@ -0,0 +1 @@
+../snippets
diff --git a/distr_tracing/distr_tracing_arch/snippets b/distr_tracing/distr_tracing_arch/snippets
@@ -0,0 +1 @@
+../../snippets/
diff --git a/distr_tracing/distr_tracing_config/snippets b/distr_tracing/distr_tracing_config/snippets
@@ -0,0 +1 @@
+../../snippets/
diff --git a/distr_tracing/distr_tracing_install/snippets b/distr_tracing/distr_tracing_install/snippets
@@ -0,0 +1 @@
+../../snippets/
diff --git a/distr_tracing/snippets b/distr_tracing/snippets
@@ -0,0 +1 @@
+../snippets/
diff --git a/getting_started/snippets b/getting_started/snippets
@@ -0,0 +1 @@
+../snippets
diff --git a/identity_providers/snippets b/identity_providers/snippets
@@ -0,0 +1 @@
+../snippets
diff --git a/installing/snippets b/installing/snippets
@@ -0,0 +1 @@
+../snippets
diff --git a/jaeger/jaeger_arch/snippets b/jaeger/jaeger_arch/snippets
@@ -0,0 +1 @@
+../snippets/
diff --git a/jaeger/jaeger_config/snippets b/jaeger/jaeger_config/snippets
@@ -0,0 +1 @@
+../snippets/
diff --git a/jaeger/jaeger_install/snippets b/jaeger/jaeger_install/snippets
@@ -0,0 +1 @@
+../snippets/
diff --git a/jaeger/snippets b/jaeger/snippets
@@ -0,0 +1 @@
+../snippets
diff --git a/kubefed/snippets b/kubefed/snippets
@@ -0,0 +1 @@
+../snippets/
diff --git a/kubefed/understanding-kubefed.adoc b/kubefed/understanding-kubefed.adoc
@@ -6,7 +6,7 @@ include::modules/kubefed-document-attributes.adoc[]
 :context: understanding-kubefed
 
 :FeatureName: Red Hat OpenShift Kubernetes Cluster Federation (KubeFed)
-include::modules/technology-preview.adoc[leveloffset=+1]
+include::snippets/technology-preview.adoc[leveloffset=+1]
 
 {KubeFedProductName} is based on the open source Kubernetes Cluster Federation (KubeFed) project.
 It enables coordinated and centrally managed configuration for multiple clusters in a federated {product-title} deployment through a single API interface.

diff --git a/logging/snippets b/logging/snippets
@@ -0,0 +1 @@
+../snippets
diff --git a/machine_management/snippets b/machine_management/snippets
@@ -0,0 +1 @@
+../snippets
diff --git a/metering/snippets b/metering/snippets
@@ -0,0 +1 @@
+../snippets
diff --git a/metrics/snippets b/metrics/snippets
@@ -0,0 +1 @@
+../snippets
diff --git a/migrating_from_ocp_3_to_4/snippets b/migrating_from_ocp_3_to_4/snippets
@@ -0,0 +1 @@
+../snippets
diff --git a/migration_toolkit_for_containers/snippets b/migration_toolkit_for_containers/snippets
@@ -0,0 +1 @@
+../snippets
diff --git a/mod_docs_guide/snippets b/mod_docs_guide/snippets
@@ -0,0 +1 @@
+../snippets
diff --git a/modules/snippets b/modules/snippets
@@ -0,0 +1 @@
+../snippets/
diff --git a/monitoring/application-monitoring.adoc b/monitoring/application-monitoring.adoc
@@ -9,7 +9,7 @@ toc::[]
 You can configure custom metrics scraping for your applications. For that, you deploy the Prometheus Operator and a custom Prometheus instance and Alertmanager instance in the namespace where your application is.
 
 :FeatureName: Application monitoring
-include::modules/technology-preview.adoc[leveloffset=+0]
+include::snippets/technology-preview.adoc[leveloffset=+0]
 
 include::modules/monitoring-configuring-cluster-for-application-monitoring.adoc[leveloffset=+1]
 include::modules/monitoring-configuring-monitoring-for-an-application.adoc[leveloffset=+1]

diff --git a/monitoring/configuring-hpa-for-an-application.adoc b/monitoring/configuring-hpa-for-an-application.adoc
@@ -9,7 +9,7 @@ toc::[]
 You can configure Horizontal Pod Autoscaling (HPA) for an application that exports metrics.
 
 :FeatureName: Horizontal Pod Autoscaling for an application
-include::modules/technology-preview.adoc[leveloffset=+0]
+include::snippets/technology-preview.adoc[leveloffset=+0]
 
 == Prerequisites
 

diff --git a/monitoring/exposing-custom-application-metrics-for-autoscaling.adoc b/monitoring/exposing-custom-application-metrics-for-autoscaling.adoc
@@ -9,7 +9,7 @@ toc::[]
 You can export custom application metrics for the horizontal pod autoscaler.
 
 :FeatureName: Prometheus Adapter
-include::modules/technology-preview.adoc[leveloffset=+0]
+include::snippets/technology-preview.adoc[leveloffset=+0]
 
 // Exposing custom application metrics for horizontal pod autoscaling
 include::modules/monitoring-exposing-custom-application-metrics-for-horizontal-pod-autoscaling.adoc[leveloffset=+1]

diff --git a/monitoring/snippets b/monitoring/snippets
@@ -0,0 +1 @@
+../snippets
diff --git a/networking/configuring-ptp.adoc b/networking/configuring-ptp.adoc
@@ -7,7 +7,7 @@ include::modules/common-attributes.adoc[]
 toc::[]
 
 :FeatureName: Precision Time Protocol (PTP) hardware
-include::modules/technology-preview.adoc[leveloffset=+1]
+include::snippets/technology-preview.adoc[leveloffset=+1]
 
 [id="about-using-ptp-hardware"]
 == About PTP hardware

diff --git a/networking/hardware_networks/snippets b/networking/hardware_networks/snippets
@@ -0,0 +1 @@
+../../snippets
diff --git a/networking/hardware_networks/using-dpdk-and-rdma.adoc b/networking/hardware_networks/using-dpdk-and-rdma.adoc
@@ -12,10 +12,10 @@ You can use Single Root I/O Virtualization (SR-IOV) network hardware with the Da
 == Examples of using virtual functions in DPDK and RDMA modes
 
 :FeatureName: The Data Plane Development Kit (DPDK)
-include::modules/technology-preview.adoc[leveloffset=+0]
+include::snippets/technology-preview.adoc[leveloffset=+0]
 
 :FeatureName: Remote Direct Memory Access (RDMA)
-include::modules/technology-preview.adoc[leveloffset=+0]
+include::snippets/technology-preview.adoc[leveloffset=+0]
 
 == Prerequisites
 

diff --git a/networking/k8s_nmstate/snippets b/networking/k8s_nmstate/snippets
@@ -0,0 +1 @@
+../../snippets
diff --git a/networking/multiple_networks/snippets b/networking/multiple_networks/snippets
@@ -0,0 +1 @@
+../../snippets/
diff --git a/networking/ovn_kubernetes_network_provider/snippets b/networking/ovn_kubernetes_network_provider/snippets
@@ -0,0 +1 @@
+../../snippets/
diff --git a/networking/snippets b/networking/snippets
@@ -0,0 +1 @@
+../snippets
diff --git a/nodes/nodes/snippets b/nodes/nodes/snippets
@@ -0,0 +1 @@
+../../snippets
diff --git a/nodes/pods/nodes-pods-vertical-autoscaler.adoc b/nodes/pods/nodes-pods-vertical-autoscaler.adoc
@@ -13,7 +13,7 @@ The {product-title} Vertical Pod Autoscaler Operator (VPA) automatically reviews
 The VPA helps you to understand the optimal CPU and memory usage for your pods and can automatically maintain pod resources through the pod lifecycle.
 
 :FeatureName: vertical pod autoscaler
-include::modules/technology-preview.adoc[leveloffset=+1]
+include::snippets/technology-preview.adoc[leveloffset=+1]
 
 // The following include statements pull in the module files that comprise
 // the assembly. Include any combination of concept, procedure, or reference

diff --git a/nodes/pods/snippets b/nodes/pods/snippets
@@ -0,0 +1 @@
+../../snippets/
diff --git a/nodes/scheduling/nodes-descheduler.adoc b/nodes/scheduling/nodes-descheduler.adoc
@@ -9,7 +9,7 @@ toc::[]
 While the xref:../../nodes/scheduling/nodes-scheduler-about.adoc#nodes-scheduler-about[scheduler] is used to determine the most suitable node to host a new pod, the descheduler can be used to evict a running pod so that the pod can be rescheduled onto a more suitable node.
 
 :FeatureName: The descheduler
-include::modules/technology-preview.adoc[leveloffset=+0]
+include::snippets/technology-preview.adoc[leveloffset=+0]
 
 // About the descheduler
 include::modules/nodes-descheduler-about.adoc[leveloffset=+1]

diff --git a/nodes/scheduling/snippets b/nodes/scheduling/snippets
@@ -0,0 +1 @@
+../../snippets/
diff --git a/nodes/snippets b/nodes/snippets
@@ -0,0 +1 @@
+../snippets
diff --git a/openshift_images/snippets b/openshift_images/snippets
@@ -0,0 +1 @@
+../snippets
diff --git a/operators/snippets b/operators/snippets
@@ -0,0 +1 @@
+../snippets
diff --git a/osd_architecture/snippets b/osd_architecture/snippets
@@ -0,0 +1 @@
+../snippets
diff --git a/osd_cluster_create/snippets b/osd_cluster_create/snippets
@@ -0,0 +1 @@
+../snippets
diff --git a/osd_notifications/snippets b/osd_notifications/snippets
@@ -0,0 +1 @@
+../snippets
diff --git a/osd_planning/snippets b/osd_planning/snippets
@@ -0,0 +1 @@
+../snippets
diff --git a/osd_policy/snippets b/osd_policy/snippets
@@ -0,0 +1 @@
+../snippets
diff --git a/osd_private_connections/snippets b/osd_private_connections/snippets
@@ -0,0 +1 @@
+../snippets
diff --git a/osd_quickstart/snippets b/osd_quickstart/snippets
@@ -0,0 +1 @@
+../snippets
diff --git a/pipelines/snippets b/pipelines/snippets
@@ -0,0 +1 @@
+../snippets/
diff --git a/pipelines/understanding-openshift-pipelines.adoc b/pipelines/understanding-openshift-pipelines.adoc
@@ -8,7 +8,7 @@ include::modules/pipelines-document-attributes.adoc[]
 toc::[]
 
 :FeatureName: OpenShift Pipelines
-include::modules/technology-preview.adoc[leveloffset=+1]
+include::snippets/technology-preview.adoc[leveloffset=+1]
 
 {pipelines-title} is a cloud-native, continuous integration and continuous delivery (CI/CD) solution based on Kubernetes resources. It uses Tekton building blocks to automate deployments across multiple platforms by abstracting away the underlying implementation details. Tekton introduces a number of standard Custom Resource Definitions (CRDs) for defining CI/CD pipelines that are portable across Kubernetes distributions.
 

diff --git a/planning/snippets b/planning/snippets
@@ -0,0 +1 @@
+../snippets
diff --git a/post_installation_configuration/snippets b/post_installation_configuration/snippets
@@ -0,0 +1 @@
+../snippets
diff --git a/registry/snippets b/registry/snippets
@@ -0,0 +1 @@
+../snippets
diff --git a/release_notes/snippets b/release_notes/snippets
@@ -0,0 +1 @@
+../snippets
diff --git a/rosa_architecture/snippets b/rosa_architecture/snippets
@@ -0,0 +1 @@
+../snippets
diff --git a/rosa_cli/snippets b/rosa_cli/snippets
@@ -0,0 +1 @@
+../snippets
diff --git a/rosa_getting_started/snippets b/rosa_getting_started/snippets
@@ -0,0 +1 @@
+../snippets
diff --git a/rosa_getting_started_sts/snippets b/rosa_getting_started_sts/snippets
@@ -0,0 +1 @@
+../snippets
diff --git a/rosa_planning/snippets b/rosa_planning/snippets
@@ -0,0 +1 @@
+../snippets
diff --git a/rosa_policy/snippets b/rosa_policy/snippets
@@ -0,0 +1 @@
+../snippets
diff --git a/rosa_support/snippets b/rosa_support/snippets
@@ -0,0 +1 @@
+../snippets
diff --git a/router/snippets b/router/snippets
@@ -0,0 +1 @@
+../snippets
diff --git a/sandboxed_containers/snippets b/sandboxed_containers/snippets
@@ -0,0 +1 @@
+../snippets
diff --git a/scalability_and_performance/snippets b/scalability_and_performance/snippets
@@ -0,0 +1 @@
+../snippets
diff --git a/security/snippets b/security/snippets
@@ -0,0 +1 @@
+../snippets
diff --git a/serverless/admin_guide/serverless-kafka-admin.adoc b/serverless/admin_guide/serverless-kafka-admin.adoc
@@ -21,7 +21,7 @@ The `KnativeKafka` CR provides users with additional options, such as:
 * Kafka broker
 
 :FeatureName: Kafka broker
-include::modules/technology-preview.adoc[leveloffset=+1]
+include::snippets/technology-preview.adoc[leveloffset=+1]
 
 include::modules/serverless-install-kafka-odc.adoc[leveloffset=+1]
 

diff --git a/serverless/admin_guide/snippets b/serverless/admin_guide/snippets
@@ -0,0 +1 @@
+../../snippets/