Merge pull request #45328 from JStickler/OSSMDOC-571

OSSMDOC-571: PoC for using snippet to create out of support banner.

Author: JStickler

service_mesh/v1x/installing-ossm.adoc

@@ -6,6 +6,8 @@ include::_attributes/common-attributes.adoc[]
 
 toc::[]
 
+include::snippets/ossm-out-of-support.adoc[]
+
 Installing the {SMProductShortName} involves installing the OpenShift Elasticsearch, Jaeger, Kiali and {SMProductShortName} Operators, creating and managing a `ServiceMeshControlPlane` resource to deploy the control plane, and creating a `ServiceMeshMemberRoll` resource to specify the namespaces associated with the {SMProductShortName}.
 
 [NOTE]

service_mesh/v1x/ossm-architecture.adoc

@@ -6,6 +6,8 @@ include::_attributes/common-attributes.adoc[]
 
 toc::[]
 
+include::snippets/ossm-out-of-support.adoc[]
+
 {SMProductName} provides a platform for behavioral insight and operational control over your networked microservices in a service mesh. With {SMProductName}, you can connect, secure, and monitor microservices in your {product-title} environment.
 
 include::modules/ossm-understanding-service-mesh.adoc[leveloffset=+1]

service_mesh/v1x/ossm-config.adoc

@@ -6,6 +6,8 @@ include::_attributes/common-attributes.adoc[]
 
 toc::[]
 
+include::snippets/ossm-out-of-support.adoc[]
+
 After you create a `ServiceMeshControlPlane` resource, configure the resource to suit your environment and requirements.
 
 This guide references the Bookinfo sample application to provide examples of security in an example application. Install the xref:../../service_mesh/v2x/prepare-to-deploy-applications-ossm.adoc#ossm-tutorial-bookinfo-overview_deploying-applications-ossm[Bookinfo application] to learn how these routing examples work.

service_mesh/v1x/ossm-custom-resources.adoc

@@ -6,6 +6,8 @@ include::_attributes/common-attributes.adoc[]
 
 toc::[]
 
+include::snippets/ossm-out-of-support.adoc[]
+
 You can customize your {SMProductName} by modifying the default {SMProductShortName} custom resource or by creating a new custom resource.
 
 == Prerequisites

service_mesh/v1x/ossm-observability.adoc

@@ -6,6 +6,8 @@ include::_attributes/common-attributes.adoc[]
 
 toc::[]
 
+include::snippets/ossm-out-of-support.adoc[]
+
 You can view your application's topology, health and metrics in the Kiali console. If your service is having issues, the Kiali console offers ways to visualize the data flow through your service. You can view insights about the mesh components at different levels, including abstract applications, services, and workloads. It also provides an interactive graph view of your namespace in real time.
 
 .Before you begin

service_mesh/v1x/ossm-security.adoc

@@ -6,6 +6,8 @@ include::_attributes/common-attributes.adoc[]
 
 toc::[]
 
+include::snippets/ossm-out-of-support.adoc[]
+
 If your service mesh application is constructed with a complex array of microservices, you can use {SMProductName} to customize the security of the communication between those services. The infrastructure of {product-title} along with the traffic management features of {SMProductShortName} can help you manage the complexity of your applications and provide service and identity security for microservices.
 
 include::modules/ossm-security-mtls-1x.adoc[leveloffset=+1]

service_mesh/v1x/ossm-traffic-manage.adoc

@@ -6,6 +6,8 @@ include::_attributes/common-attributes.adoc[]
 
 toc::[]
 
+include::snippets/ossm-out-of-support.adoc[]
+
 You can control the flow of traffic and API calls between services in  {SMProductName}. For example, some services in your service mesh may need to communicate within the mesh and others may need to be hidden. Manage the traffic to hide specific backend services, expose services, create testing or versioning deployments, or add a security layer on a set of services.
 
 This guide references the Bookinfo sample application to provide examples of routing in an example application. Install the xref:../../service_mesh/v1x/prepare-to-deploy-applications-ossm.adoc#ossm-tutorial-bookinfo-overview_deploying-applications-ossm-v1x[Bookinfo application] to learn how these routing examples work.
@@ -20,6 +22,6 @@ include::modules/ossm-routing-ingress.adoc[leveloffset=+1]
 
 include::modules/ossm-auto-route-1x.adoc[leveloffset=+1]
 
-== Links 
+== Links
 
 For more information about configuring an {product-title} wildcard policy, see xref:../../networking/ingress-operator.adoc#using-wildcard-routes_configuring-ingress[Using wildcard routes].

service_mesh/v1x/ossm-vs-community.adoc

@@ -6,6 +6,8 @@ include::_attributes/common-attributes.adoc[]
 
 toc::[]
 
+include::snippets/ossm-out-of-support.adoc[]
+
 An installation of {SMProductName} differs from upstream Istio community installations in multiple ways. The modifications to {SMProductName} are sometimes necessary to resolve issues, provide additional features, or to handle differences when deploying on {product-title}.
 
 The current release of {SMProductName} differs from the current upstream Istio community release in the following ways:

service_mesh/v1x/prepare-to-deploy-applications-ossm.adoc

@@ -6,6 +6,8 @@ include::_attributes/common-attributes.adoc[]
 
 toc::[]
 
+include::snippets/ossm-out-of-support.adoc[]
+
 When you deploy an application into the {SMProductShortName}, there are several differences between the behavior of applications in the upstream community version of Istio and the behavior of applications within a {SMProductName} installation.
 
 == Prerequisites

service_mesh/v1x/preparing-ossm-installation.adoc

@@ -6,6 +6,8 @@ include::_attributes/common-attributes.adoc[]
 
 toc::[]
 
+include::snippets/ossm-out-of-support.adoc[]
+
 Before you can install {SMProductName}, review the installation activities, ensure that you meet the prerequisites:
 
 == Prerequisites