Merge pull request #33416 from kalexand-rh/BZ1881856

BZ1881856: why you shouldn't modify the default SCCs

Author: kalexand-rh

modules/security-context-constraints-about.adoc

@@ -53,8 +53,7 @@ effectively root on the cluster and must be trusted accordingly.
 
 [IMPORTANT]
 ====
-Do not modify the default SCCs. Customizing the default SCCs can lead to issues
-when {product-title} is upgraded.
+Do not modify the default SCCs. Customizing the default SCCs can lead to issues when some of the platform pods deploy or {product-title} is upgraded. During upgrades between some versions of {product-title}, the values of the default SCCs are reset to the default values, which discards all customizations to those SCCs.
 ifdef::openshift-origin,openshift-enterprise,openshift-webscale[]
 Instead, create new SCCs.
 endif::[]

modules/security-context-constraints-command-reference.adoc

@@ -15,8 +15,7 @@ You must have `cluster-admin` privileges to manage SCCs.
 
 [IMPORTANT]
 ====
-Do not modify the default SCCs. Customizing the default SCCs can lead to issues
-when upgrading. Instead, create new SCCs.
+Do not modify the default SCCs. Customizing the default SCCs can lead to issues when some of the platform pods deploy or {product-title} is upgraded. During upgrades between some versions of {product-title}, the values of the default SCCs are reset to the default values, which discards all customizations to those SCCs.
 ====
 endif::openshift-enterprise,openshift-webscale,openshift-origin[]