Skip to content

Commit 40be28b

Browse files
committed
corrections after review
1 parent 03ceca9 commit 40be28b

File tree

1 file changed

+7
-7
lines changed

1 file changed

+7
-7
lines changed

articles/openshift/howto-run-privileged-containers.md

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -13,7 +13,7 @@ keywords: aro, openshift, aquasec, twistlock, red hat
1313
# Run privileged containers in an Azure Red Hat OpenShift cluster
1414

1515
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.
1717
This document describes the differences from the generic OpenShift deployment documentation of the security product vendors.
1818

1919

@@ -26,10 +26,10 @@ The documentation of most security products assumes you have cluster-admin privi
2626
Customer admins don't have all privileges in Azure Red Hat OpenShift. Permissions to modify cluster-wide resources are limited.
2727

2828
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.
3030

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).
3333

3434
The first step is to annotate the SCCs you're editing. These annotations will prevent the Sync Pod from reverting your changes.
3535

@@ -98,7 +98,7 @@ Set the following fields when deploying enforcers:
9898

9999
## Product-specific steps for Prisma Cloud / Twistlock
100100

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)
102102

103103
Start by creating a new OpenShift project
104104
```
@@ -114,8 +114,8 @@ You can safely ignore it, the namespace has been created with the `oc new-projec
114114

115115
### Create an external route to Console
116116

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
119119
```
120120
apiVersion: route.openshift.io/v1
121121
kind: Route

0 commit comments

Comments
 (0)