Merge pull request #95038 from kcarmichael08/ROX-29352-policy-as-code-ga

ROX-29352: Remove Technology Preview labels from policy as code

Author: kcarmichael08

installing/installing_ocp/install-central-ocp.adoc

@@ -112,3 +112,4 @@ include::modules/install-roxctl-cli-windows.adoc[leveloffset=+3]
 include::modules/using-the-interactive-installer.adoc[leveloffset=+2]
 
 include::modules/install-central-roxctl.adoc[leveloffset=+2]
+

installing/installing_other/install-central-other.adoc

@@ -80,3 +80,4 @@ include::modules/install-roxctl-cli-windows.adoc[leveloffset=+3]
 include::modules/using-the-interactive-installer.adoc[leveloffset=+2]
 
 include::modules/install-central-roxctl.adoc[leveloffset=+2]
+

modules/install-central-roxctl.adoc

@@ -2,6 +2,7 @@
 //
 // * installing/install_ocp/install-central-ocp.adoc
 // * installing/install_other/install-central-other.adoc
+// * backup_and_restore/restore-acs.htm
 :_mod-docs-content-type: PROCEDURE
 [id="install-central-roxctl_{context}"]
 = Running the Central installation scripts
@@ -14,6 +15,10 @@ ifeval::["{context}" == "install-central-other"]
 :kube:
 endif::[]
 
+ifeval::["{context}" == "restore-acs"]
+:openshift:
+endif::[]
+
 After you run the interactive installer, you can run the `setup.sh` script to install Central.
 
 .Procedure
@@ -23,27 +28,6 @@ After you run the interactive installer, you can run the `setup.sh` script to in
 ----
 $ ./central-bundle/central/scripts/setup.sh
 ----
-. To enable the policy as code feature (Technology Preview), manually apply the `config.stackrox.io` CRD that is located in the .zip file at `helm/chart/crds/config.stackrox.io_securitypolicies.yaml`.
-+
---
-:FeatureName: Policy as code
-include::snippets/technology-preview.adoc[]
-
-To apply the CRD, run the following command:
-
-ifdef::openshift[]
-[source,terminal]
-----
-$ oc create -f helm/chart/crds/config.stackrox.io_securitypolicies.yaml
-----
-endif::openshift[]
-ifdef::kube[]
-[source,terminal]
-----
-$ kubectl create -f helm/chart/crds/config.stackrox.io_securitypolicies.yaml
-----
-endif::kube[]
---
 . Create the necessary resources:
 +
 ifdef::openshift[]

modules/policy-as-code-about.adoc

@@ -9,9 +9,6 @@
 
 You can create and manage policies as code by saving policies as Kubernetes custom resources (CRs) and applying them to clusters by using a Kubernetes-native continuous delivery (CD) tool such as Argo CD.
 
-:FeatureName: Policy as code
-include::snippets/technology-preview.adoc[]
-
 Policy as code is useful for Kubernetes security architects who want to author policies in YAML or JSON instead of using the {product-title-short} portal. GitOps administrators who already manage Kubernetes configurations by using a GitOps workflow can also find it useful.
 
 {product-title-short} provides the ability to use default policies or create custom policies for your system. With the policy as code feature, you can create custom policies locally by downloading them and modifying them, or by creating them from empty files. To author policies locally, you create CRs that represent the desired state of the policies. You then use a continuous delivery tool such as Argo CD to track, manage, and apply policies to your clusters that are running {product-title-short}. After you create or update CRs and use the CI/CD tool to apply them, the policies stored in the {product-title-short} database are created or updated.

modules/upgrade-central-cluster-crds.adoc

@@ -2,7 +2,7 @@
 //
 // * upgrade/upgrade-roxctl.adoc
 :_mod-docs-content-type: PROCEDURE
-[id="upgrade-central-cluster-crds{context}"]
+[id="upgrade-central-cluster-crds_{context}"]
 = Upgrading the SecurityPolicy custom resource definition
 
 [role="_abstract"]

modules/upgrade-crd-helm.adoc

@@ -2,7 +2,7 @@
 //
 // * upgrading/upgrade-helm.adoc
 :_mod-docs-content-type: PROCEDURE
-[id="upgrade-crd-helm{context}"]
+[id="upgrade-crd-helm_{context}"]
 = Preparing the custom resource definition for upgrade
 
 [role="_abstract"]