Skip to content

ROX-24744: Update docs with namespace exclusions for admission controller #100954

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-24744: Update docs with namespace exclusions for admission controller #100954

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
24 changes: 21 additions & 3 deletions modules/namespace-exclusions.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -6,8 +6,26 @@

:_mod-docs-content-type: CONCEPT
[id="namespace-exclusions_{context}"]
= Namespace exclusions
= Namespace exclusions from admission controller enforcement

By default, {product-title-short} excludes certain administrative namespaces, such as the `stackrox`, `kube-system`, and `istio-system` namespaces, from enforcement blocking. The reason for this is that some items in these namespaces must be deployed for {product-title-short} to work correctly.
[role="_abstract"]
By default, {product-title-short} excludes certain administrative namespaces, such as the `stackrox`, `kube-system`, and `istio-system` namespaces, from admission controller enforcement blocking. The reason for this is that some items in these namespaces must be deployed for {product-title-short} to work correctly.

In addition, the {product-title-short} admission controller bypasses requests that originate from a `service` account in a `system` namespace. Consider this factor when deploying the CI/CD tool of your choice.
These exclusions mean that API calls for these namespaces are not passed to {product-title-short} for review. Instead of rejecting the `CREATE` verb, the deployment is created and then scaled down using Sensor.

There are two places where excluded namespaces are defined:

* The configuration of the `ValidatingWebhookConfiguration`
* The {product-title-short} code that defines "system" namespaces

The following namespaces are excluded:

* `stackrox`
* `kube.*`
* `kube-system`
* `kube-public`
* `istio-system`
* `openshift.*`
* `redhat.*`

In addition to excluding namespaces, the {product-title-short} admission controller bypasses requests that originate from a `service` account in a `system` namespace. Consider this factor when deploying the CI/CD tool of your choice.