Merge pull request #100979 from maxwelldb/enterprise-4.17

[OSDOCS#16526] Revert rm of troublesome snippets - 4.17

Author: maxwelldb

snippets/imp-rosa-hcp-no-shared-vpc-support.adoc

@@ -0,0 +1,4 @@
+[IMPORTANT]
+====
+link:https://docs.aws.amazon.com/vpc/latest/userguide/vpc-sharing.html[Sharing VPCs across multiple AWS accounts] is not currently supported for {hcp-title}. Do not install a {hcp-title} cluster into subnets shared from another AWS account. See link:https://access.redhat.com/solutions/6980058["Are multiple ROSA clusters in a single VPC supported?"] for more information.
+====

snippets/olmv1-known-issue-service-accounts.adoc

@@ -0,0 +1,14 @@
+// Text snippet included in the following modules:
+//
+// * modules/olmv1-installing-an-operator.adoc
+// * release_notes/ocp-4-17-release-notes.adoc (enterprise-4.17 branch only)
+
+:_mod-docs-content-type: SNIPPET
+
+There is a known issue in {olmv1}. If you do not assign the correct role-based access controls (RBAC) to an extension's service account, {olmv1} gets stuck and reconciliation stops.
+
+Currently, {olmv1} does not have tools to help extension administrators find the correct RBAC for a service account.
+
+Because {olmv1} is a Technology Preview feature and must not be used on production clusters, you can avoid this issue by using the more permissive RBAC included in the documentation.
+
+This RBAC is intended for testing purposes only. Do not use it on production clusters.

snippets/olmv1-secure-registry-pull-secret.adoc

@@ -0,0 +1,15 @@
+// Text snippet included in the following modules:
+//
+// * modules/olmv1-adding-a-catalog.adoc
+// * modules/olmv1-creating-a-pull-secret-for-catalogd.adoc
+// * modules/olmv1-red-hat-catalogs.adoc
+
+:_mod-docs-content-type: SNIPPET
+
+If you want to use a catalog that is hosted on a private registry, such as Red{nbsp}Hat-provided Operator catalogs from `registry.redhat.io`, you must have a pull secret scoped to the `openshift-catalogd` namespace.
+
+ifndef::olmv1-pullsecret-proc[For more information, see "Creating a pull secret for catalogs hosted on a secure registry".]
+
+ifdef::olmv1-pullsecret-proc[]
+Catalogd cannot read global pull secrets from {product-title} clusters. Catalogd can read references to secrets only in the namespace where it is deployed.
+endif::[]

snippets/rosa-hcp-rn.adoc

@@ -0,0 +1,6 @@
+// Text snippet included in the following modules:
+//
+// * rosa_release_notes/rosa-release-notes.adoc
+
+:_mod-docs-content-type: SNIPPET
+* **Hosted control planes.** {hcp-title-first} clusters are now available as a link:https://access.redhat.com/support/offerings/techpreview[Technology Preview] feature. This new architecture provides a lower-cost, more resilient ROSA architecture. For more information, see xref:../rosa_hcp/rosa-hcp-sts-creating-a-cluster-quickly.adoc#rosa-hcp-sts-creating-a-cluster-quickly[Creating {hcp-title} clusters using the default options].