Merge pull request #29324 from sagidlow/BZ1801331

Updated per BZ1801331

Author: kalexand-rh

applications/projects/working-with-projects.adoc

@@ -13,6 +13,11 @@ isolation from other communities.
 Projects starting with `openshift-` and `kube-` are  xref:../../authentication/using-rbac.adoc#rbac-default-projects_using-rbac[default projects]. These projects host cluster components that run as pods and other infrastructure components. As such, {product-title} does not allow you to create projects starting with `openshift-` or `kube-` using the `oc new-project` command. Cluster administrators can create these projects using the `oc adm new-project` command.
 ====
 
+[NOTE]
+====
+You cannot assign an SCC to pods created in one of the default namespaces: `default`, `kube-system`, `kube-public`, `openshift-node`, `openshift-infra`, and `openshift`. You cannot use these namespaces for running pods or services.
+====
+
 include::modules/creating-a-project-using-the-web-console.adoc[leveloffset=+1]
 
 include::modules/odc-creating-projects-using-developer-perspective.adoc[leveloffset=+1]

modules/creating-a-project-using-the-CLI.adoc

@@ -12,6 +12,11 @@ If allowed by your cluster administrator, you can create a new project.
 Projects starting with `openshift-` and `kube-` are considered critical by {product-title}. As such, {product-title} does not allow you to create Projects starting with `openshift-` or `kube-` using the `oc new-project` command. Cluster administrators can create these Projects using the `oc adm new-project` command.
 ====
 
+[NOTE]
+====
+You cannot assign an SCC to pods created in one of the default namespaces: `default`, `kube-system`, `kube-public`, `openshift-node`, `openshift-infra`, and `openshift`. You cannot use these namespaces for running pods or services.
+====
+
 .Procedure
 
 . Run:

modules/creating-a-project-using-the-web-console.adoc

@@ -12,6 +12,11 @@ If allowed by your cluster administrator, you can create a new project.
 Projects starting with `openshift-` and `kube-` are considered critical by {product-title}. As such, {product-title} does not allow you to create Projects starting with `openshift-` using the web console.
 ====
 
+[NOTE]
+====
+You cannot assign an SCC to pods created in one of the default namespaces: `default`, `kube-system`, `kube-public`, `openshift-node`, `openshift-infra`, and `openshift`. You cannot use these namespaces for running pods or services.
+====
+
 .Procedure
 
 . Navigate to *Home* -> *Projects*.

modules/odc-creating-projects-using-developer-perspective.adoc

@@ -12,6 +12,11 @@ You can use the *Developer* perspective in the {product-title} web console to cr
 Projects starting with `openshift-` and `kube-` are considered critical by {product-title}. As such, {product-title} does not allow you to create projects starting with `openshift-` or `kube-` using the *Developer* perspective. Cluster administrators can create these projects using the `oc adm new-project` command.
 ====
 
+[NOTE]
+====
+You cannot assign an SCC to pods created in one of the default namespaces: `default`, `kube-system`, `kube-public`, `openshift-node`, `openshift-infra`, and `openshift`. You cannot use these namespaces for running pods or services.
+====
+
 .Prerequisites
 
 * Ensure that you have the appropriate link:https://docs.openshift.com/container-platform/latest/authentication/using-rbac.html#default-roles_using-rbac[roles and permissions] to create projects, applications, and other workloads in {product-title}.

modules/rbac-default-projects.adoc

@@ -14,3 +14,8 @@ link:https://kubernetes.io/docs/tasks/administer-cluster/guaranteed-scheduling-c
 are considered critical, and the have guaranteed admission by kubelet.
 Pods created for master components in these namespaces are already marked as
 critical.
+
+[NOTE]
+====
+You cannot assign an SCC to pods created in one of the default namespaces: `default`, `kube-system`, `kube-public`, `openshift-node`, `openshift-infra`, and `openshift`. You cannot use these namespaces for running pods or services.
+====