Skip to content

Commit 7769e81

Browse files
committed
Remove Technology Preview labels from policy as code
1 parent e5dcec2 commit 7769e81

File tree

2 files changed

+1
-6
lines changed

2 files changed

+1
-6
lines changed

modules/install-central-roxctl.adoc

Lines changed: 1 addition & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -23,11 +23,9 @@ After you run the interactive installer, you can run the `setup.sh` script to in
2323
----
2424
$ ./central-bundle/central/scripts/setup.sh
2525
----
26-
. 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`.
26+
. To enable the policy as code feature, manually apply the `config.stackrox.io` CRD that is located in the .zip file at `helm/chart/crds/config.stackrox.io_securitypolicies.yaml`.
2727
+
2828
--
29-
:FeatureName: Policy as code
30-
include::snippets/technology-preview.adoc[]
3129

3230
To apply the CRD, run the following command:
3331

modules/policy-as-code-about.adoc

Lines changed: 0 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -9,9 +9,6 @@
99

1010
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.
1111

12-
:FeatureName: Policy as code
13-
include::snippets/technology-preview.adoc[]
14-
1512
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.
1613

1714
{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.

0 commit comments

Comments
 (0)