Skip to content

[rhacs-docs-4.9] fix errors in admission controller 4.9 docs #101121

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

Merged
kcarmichael08 merged 1 commit into from
Oct 27, 2025
Merged

[rhacs-docs-4.9] fix errors in admission controller 4.9 docs #101121

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
2 changes: 1 addition & 1 deletion modules/admission-controller-failure-policy-changing.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -8,7 +8,7 @@
[role="_abstract"]
You can configure the admission controller failure policy for an existing cluster. This setting determines whether the API server request is allowed (fail open) or blocked (fail closed) if an error or timeout happens in the {product-title-short} validating webhook evaluation.

. For a cluster that was installed by using the Operator, in the `SecuredCluster` custom resource (CR), edit the `admissionControl.failurePolicy` parameter to `Ignore` to fail open, or `Fail` to fail closed.
. For a cluster that was installed by using the Operator, in the `SecuredCluster` custom resource (CR), edit the `spec.admissionControl.failurePolicy` parameter to `Ignore` to fail open, or `Fail` to fail closed.
. For a cluster that was installed by using Helm, in the `values-public.yaml` file, set the `admissionControl.failurePolicy` value to parameter to `Ignore` to fail open, or `Fail` to fail closed. Then then run the following command:
+
[source,terminal]
Expand Down
2 changes: 1 addition & 1 deletion modules/disable-admission-controller-enforcement.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -9,7 +9,7 @@
You can disable admission controller enforcement on a cluster when installing {product-title-short}. For clusters that you did not install by using the Operator or Helm, you can disable admission controller enforcement from the *Clusters* view on the {product-title} ({product-title-short}) portal.

.Procedure
. For a cluster that was installed by using the Operator, in the `SecuredCluster` custom resource (CR), edit the `admissionControl.enforcement` parameter to `Disabled`.
. For a cluster that was installed by using the Operator, in the `SecuredCluster` custom resource (CR), edit the `spec.admissionControl.enforcement` parameter to `Disabled`.
. For a cluster that was installed by using Helm, in the `values-public.yaml` file, set the `admissionControl.enforce` value to `false` and run the following command:
+
[source,terminal]
Expand Down
2 changes: 1 addition & 1 deletion modules/enable-admission-controller-enforcement-existing-cluster.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -10,7 +10,7 @@ You can view whether admission controller enforcement was enabled on a cluster o

.Procedure

. For a cluster that was installed by using the Operator, in the `SecuredCluster` custom resource (CR), edit the `admissionControl.enforcement` parameter to `Enabled`.
. For a cluster that was installed by using the Operator, in the `SecuredCluster` custom resource (CR), edit the `spec.admissionControl.enforcement` parameter to `Enabled`.
. For a cluster that was installed by using Helm, in the `values-public.yaml` file, set the `admissionControl.enforce` value to `false` and run the following command:
+
[source,terminal]
Expand Down