From c05b44cd56a18ec9ab0616511ef35152198299c3 Mon Sep 17 00:00:00 2001 From: Anatolii Bazko Date: Wed, 25 Mar 2026 10:49:35 +0100 Subject: [PATCH 1/3] procedures: document direct namespace creation on OpenShift Co-Authored-By: Claude Opus 4.6 --- modules/administration-guide/nav.adoc | 1 + ...irect-namespace-creation-on-openshift.adoc | 44 +++++++++++++++++++ 2 files changed, 45 insertions(+) create mode 100644 modules/administration-guide/pages/configuring-direct-namespace-creation-on-openshift.adoc diff --git a/modules/administration-guide/nav.adoc b/modules/administration-guide/nav.adoc index 6b19ae5c1f..e8c2df46fe 100644 --- a/modules/administration-guide/nav.adoc +++ b/modules/administration-guide/nav.adoc @@ -41,6 +41,7 @@ *** xref:configuring-workspace-target-namespace.adoc[] *** xref:provisioning-namespaces-in-advance.adoc[] *** xref:configuring-a-user-namespace.adoc[] +*** xref:configuring-direct-namespace-creation-on-openshift.adoc[] ** xref:configuring-server-components.adoc[] *** xref:mounting-a-secret-as-a-file-or-an-environment-variable-into-a-container.adoc[] *** xref:advanced-configuration-options-for-the-che-server-component.adoc[] diff --git a/modules/administration-guide/pages/configuring-direct-namespace-creation-on-openshift.adoc b/modules/administration-guide/pages/configuring-direct-namespace-creation-on-openshift.adoc new file mode 100644 index 0000000000..a609ec0afe --- /dev/null +++ b/modules/administration-guide/pages/configuring-direct-namespace-creation-on-openshift.adoc @@ -0,0 +1,44 @@ +:_content-type: PROCEDURE +:description: Configuring {prod-short} to create standard {kubernetes} Namespaces directly on {ocp} instead of using the ProjectRequest API +:keywords: administration guide, configuring, namespace, openshift, project, projectrequest +:navtitle: Configuring direct namespace creation on OpenShift +:page-aliases: + +[id="configuring-direct-namespace-creation-on-openshift"] += Configuring direct namespace creation on OpenShift + +By default, on {ocp} clusters, {prod-short} uses the ProjectRequest API to create user namespaces. This triggers cluster-specific link:https://docs.openshift.com/container-platform/latest/applications/projects/configuring-project-creation.html[Project Templates], which may apply additional resources or policies to newly created projects. + +In some environments, you may want to bypass Project Templates and create standard {kubernetes} Namespaces directly. For example, this is useful when Project Templates introduce unwanted side effects or when you need consistent namespace provisioning behavior across {kubernetes} and {ocp} clusters. + +.Prerequisites + +* An active `{orch-cli}` session with administrative permissions to the destination {orch-name} cluster. See {orch-cli-link}. + +.Procedure + +. Set the `createNamespaceDirectly` field to `true`: ++ +[source,shell,subs="+quotes,+attributes,+macros"] +---- +{orch-cli} patch checluster {prod-checluster} \ + --namespace {prod-namespace} \ + --type merge \ + --patch '{ + "spec": { + "devEnvironments": { + "defaultNamespace": { + "createNamespaceDirectly": true + } + } + } + }' +---- + +NOTE: This setting applies only to {ocp} clusters. On {kubernetes} clusters, Namespaces are always created directly regardless of this setting. + +.Additional resources + +* xref:configuring-namespace-provisioning.adoc[] +* xref:configuring-a-user-namespace.adoc[] +* link:https://docs.openshift.com/container-platform/latest/applications/projects/configuring-project-creation.html[Configuring OpenShift project creation] From cd525d20bf2ca9cfbae8ded7d0baaf54019e7ead Mon Sep 17 00:00:00 2001 From: Anatolii Bazko Date: Wed, 25 Mar 2026 10:52:45 +0100 Subject: [PATCH 2/3] fix: address vale linting warnings and errors Co-Authored-By: Claude Opus 4.6 --- .../configuring-direct-namespace-creation-on-openshift.adoc | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/modules/administration-guide/pages/configuring-direct-namespace-creation-on-openshift.adoc b/modules/administration-guide/pages/configuring-direct-namespace-creation-on-openshift.adoc index a609ec0afe..a1a8bb9be5 100644 --- a/modules/administration-guide/pages/configuring-direct-namespace-creation-on-openshift.adoc +++ b/modules/administration-guide/pages/configuring-direct-namespace-creation-on-openshift.adoc @@ -7,9 +7,9 @@ [id="configuring-direct-namespace-creation-on-openshift"] = Configuring direct namespace creation on OpenShift -By default, on {ocp} clusters, {prod-short} uses the ProjectRequest API to create user namespaces. This triggers cluster-specific link:https://docs.openshift.com/container-platform/latest/applications/projects/configuring-project-creation.html[Project Templates], which may apply additional resources or policies to newly created projects. +By default, on {ocp} clusters, {prod-short} uses the ProjectRequest API to create user namespaces. This triggers cluster-specific link:https://docs.openshift.com/container-platform/latest/applications/projects/configuring-project-creation.html[Project Templates], which can apply additional resources or policies to newly created projects. -In some environments, you may want to bypass Project Templates and create standard {kubernetes} Namespaces directly. For example, this is useful when Project Templates introduce unwanted side effects or when you need consistent namespace provisioning behavior across {kubernetes} and {ocp} clusters. +In some environments, you can bypass Project Templates and create standard {kubernetes} Namespaces directly. For example, this is useful when Project Templates introduce unwanted side effects or when you need consistent {orch-namespace} provisioning behavior across {kubernetes} and {ocp} clusters. .Prerequisites From 6f4837f6c126484fa07853bff5869b8453d2447c Mon Sep 17 00:00:00 2001 From: Anatolii Bazko Date: Wed, 25 Mar 2026 11:02:17 +0100 Subject: [PATCH 3/3] fix: refine wording in direct namespace creation article Co-Authored-By: Claude Opus 4.6 --- .../configuring-direct-namespace-creation-on-openshift.adoc | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/modules/administration-guide/pages/configuring-direct-namespace-creation-on-openshift.adoc b/modules/administration-guide/pages/configuring-direct-namespace-creation-on-openshift.adoc index a1a8bb9be5..4515cbeb6a 100644 --- a/modules/administration-guide/pages/configuring-direct-namespace-creation-on-openshift.adoc +++ b/modules/administration-guide/pages/configuring-direct-namespace-creation-on-openshift.adoc @@ -7,9 +7,9 @@ [id="configuring-direct-namespace-creation-on-openshift"] = Configuring direct namespace creation on OpenShift -By default, on {ocp} clusters, {prod-short} uses the ProjectRequest API to create user namespaces. This triggers cluster-specific link:https://docs.openshift.com/container-platform/latest/applications/projects/configuring-project-creation.html[Project Templates], which can apply additional resources or policies to newly created projects. +By default, on {ocp} clusters, {prod-short} uses the ProjectRequest API to create projects. This triggers cluster-specific link:https://docs.openshift.com/container-platform/latest/applications/projects/configuring-project-creation.html[Project Templates], which can apply additional resources or policies. -In some environments, you can bypass Project Templates and create standard {kubernetes} Namespaces directly. For example, this is useful when Project Templates introduce unwanted side effects or when you need consistent {orch-namespace} provisioning behavior across {kubernetes} and {ocp} clusters. +On {ocp}, you can bypass Project Templates and create standard {kubernetes} Namespaces directly. For example, this is useful when Project Templates introduce unwanted side effects. .Prerequisites