changed force and disable explanation

camunda · Oct 8, 2024 · f54b67a · f54b67a
1 parent 8676888
commit f54b67a
Show file tree

Hide file tree

Showing 3 changed files with 6 additions and 6 deletions.
diff --git a/docs/self-managed/operational-guides/update-guide/850-to-860.md b/docs/self-managed/operational-guides/update-guide/850-to-860.md
@@ -40,7 +40,7 @@ Avro schema support is the only breaking change for this Connector. If you do no
 
 We added the `global.compatibility.openshift.adaptSecurityContext` variable in the values.yaml that can be used to set the following possible values:
 
-- `force`: all `runAsUser` and `fsGroup` values will be set to null.
-- `disabled`: this is the default value. In this case, the `runAsUser` and `fsGroup` values will not be modified.
+- `force`:The runAsUser and fsGroup values will be null in all components.
+- `disabled`:The runAsUser and fsGroup values will not be modified (default).
 
 With this change, there is no need to do extra steps with the post-renderer. You can install the chart as normal. Please refer to the [Red Hat OpenShift document](/self-managed/setup/deploy/openshift/redhat-openshift.md) for more information.
diff --git a/docs/self-managed/setup/deploy/openshift/redhat-openshift.md b/docs/self-managed/setup/deploy/openshift/redhat-openshift.md
@@ -48,8 +48,8 @@ Depending on your OpenShift cluster's Security Context Constraints (SCCs) config
 By default, OpenShift employs more restrictive SCCs. The Helm chart must assign `null` to the user running all components and dependencies.
 The `global.compatibility.openshift.adaptSecurityContext` variable in your values.yaml can be used to set the following possible values:
 
-- `force`: all `runAsUser` and `fsGroup` values will be set to null.
-- `disabled`: this is the default value. In this case, no fields will be modified.
+- `force`:The runAsUser and fsGroup values will be null in all components.
+- `disabled`:The runAsUser and fsGroup values will not be modified (default).
 
 To deploy Camunda 8 on OpenShift:
 

diff --git a/docs/self-managed/setup/upgrade.md b/docs/self-managed/setup/upgrade.md
@@ -87,8 +87,8 @@ The separated Ingress Helm configuration has been deprecated in 8.6, and will be
 
 We added the `global.compatibility.openshift.adaptSecurityContext` variable in the values.yaml that can be used to set the following possible values:
 
-- `force`: all `runAsUser` and `fsGroup` values will be set to null.
-- `disabled`: this is the default value. In this case, the `runAsUser` and `fsGroup` values will not be modified.
+- `force`:The runAsUser and fsGroup values will be null in all components.
+- `disabled`:The runAsUser and fsGroup values will not be modified (default).
 
 With this change, there is no need to do extra steps with the post-renderer. You can install the chart as normal. Please refer to the [Red Hat OpenShift document](/self-managed/setup/deploy/openshift/redhat-openshift.md) for more information.