You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/openshift/howto-run-privileged-containers.md
+7-7Lines changed: 7 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -13,7 +13,7 @@ keywords: aro, openshift, aquasec, twistlock, red hat
13
13
# Run privileged containers in an Azure Red Hat OpenShift cluster
14
14
15
15
You can't run arbitrary privileged containers on Azure Red Hat OpenShift clusters.
16
-
Two security monitoring and compliance solutions are whitelisted to run on ARO clusters.
16
+
Two security monitoring and compliance solutions are allowed to run on ARO clusters.
17
17
This document describes the differences from the generic OpenShift deployment documentation of the security product vendors.
18
18
19
19
@@ -26,10 +26,10 @@ The documentation of most security products assumes you have cluster-admin privi
26
26
Customer admins don't have all privileges in Azure Red Hat OpenShift. Permissions to modify cluster-wide resources are limited.
27
27
28
28
Make sure you're logged in to the cluster as a customer admin, by running
29
-
`oc get scc`. All users in the customer admin group have permissions to view the SCCs on the cluster.
29
+
`oc get scc`. All users in the customer admin group have permissions to view the Security Context Constraints (SCCs) on the cluster.
30
30
31
-
## Product-specific steps for Aqua security
32
-
The base instructions we're going to modify can be found at (https://docs.aquasec.com/docs/deploy-openshift).
31
+
## Product-specific steps for Aqua Security
32
+
The base instructions we're going to modify can be found in the [Aqua Security deployment documentation](https://docs.aquasec.com/docs/deploy-openshift).
33
33
34
34
The first step is to annotate the SCCs you're editing. These annotations will prevent the Sync Pod from reverting your changes.
35
35
@@ -98,7 +98,7 @@ Set the following fields when deploying enforcers:
98
98
99
99
## Product-specific steps for Prisma Cloud / Twistlock
100
100
101
-
The base instructions we're going to modify can be found at fhttps://docs.paloaltonetworks.com/prisma/prisma-cloud/19-11/prisma-cloud-compute-edition-admin/install/install_openshift.html
101
+
The base instructions we're going to modify can be found in the [Prisma Cloud deployment documentation](https://docs.paloaltonetworks.com/prisma/prisma-cloud/19-11/prisma-cloud-compute-edition-admin/install/install_openshift.html)
102
102
103
103
Start by creating a new OpenShift project
104
104
```
@@ -114,8 +114,8 @@ You can safely ignore it, the namespace has been created with the `oc new-projec
114
114
115
115
### Create an external route to Console
116
116
117
-
You can either follow the documentation, or if you prefer to use the oc command
118
-
copy the following Route definition to a file called twistlock_route.yaml
117
+
You can either follow the documentation, or the instructions below if you prefer the oc command.
118
+
Copy the following Route definition to a file called twistlock_route.yaml on your computer
0 commit comments