Skip to content

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

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: rhacs-docs-main
Choose a base branch
from
Open

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

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
15 changes: 7 additions & 8 deletions modules/install-central-roxctl.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand All @@ -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
Expand All @@ -23,14 +28,8 @@ 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`.
. 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`. To apply the CRD, run the following command:
+
--
:FeatureName: Policy as code
include::snippets/technology-preview.adoc[]

To apply the CRD, run the following command:

ifdef::openshift[]
[source,terminal]
----
Expand All @@ -43,7 +42,7 @@ ifdef::kube[]
$ kubectl create -f helm/chart/crds/config.stackrox.io_securitypolicies.yaml
----
endif::kube[]
--

. Create the necessary resources:
+
ifdef::openshift[]
Expand Down
3 changes: 0 additions & 3 deletions modules/policy-as-code-about.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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.
Expand Down