From cd8129b3f97ad2cce9e8095a0e0ba1ad140909c1 Mon Sep 17 00:00:00 2001 From: Daniela Merlo Date: Tue, 28 Jul 2026 17:13:33 -0300 Subject: [PATCH 1/3] W-23153656-CH2-public-domain-dm --- cloudhub-2/modules/ROOT/pages/ps-config-domains.adoc | 9 +++++++++ 1 file changed, 9 insertions(+) diff --git a/cloudhub-2/modules/ROOT/pages/ps-config-domains.adoc b/cloudhub-2/modules/ROOT/pages/ps-config-domains.adoc index 76b4209b..412068df 100644 --- a/cloudhub-2/modules/ROOT/pages/ps-config-domains.adoc +++ b/cloudhub-2/modules/ROOT/pages/ps-config-domains.adoc @@ -9,6 +9,15 @@ Each private space includes one TLS context by default (for traffic to `cloudhub The default certificate renews automatically and requires no action from the user. You can create additional TLS contexts as required. +[IMPORTANT] +==== +The default `.cloudhub.io` domain is shared across all customers in a region. +Because private spaces from different customers resolve under the same `.cloudhub.io` parent domain, browsers treat them as the same site, and cookies set at that domain scope aren't isolated between customers. + +Hosting websites or other browser-facing applications isn't a supported use case for the default `cloudhub.io` domain. +To keep browser-facing applications isolated, deploy them to a customer-owned vanity domain by configuring a TLS context with your own domain and DNS records, as described in this topic. +==== + The TLS contexts that you configure for the private space define the domains that are available when deploying apps to the private spaces. See xref:ch2-config-endpoints-paths.adoc[]. From 6a2c8532559a099848a869a6a51ed6e17a272795 Mon Sep 17 00:00:00 2001 From: Daniela Merlo <97902112+dmerlob@users.noreply.github.com> Date: Tue, 28 Jul 2026 17:14:49 -0300 Subject: [PATCH 2/3] Update cloudhub-2/modules/ROOT/pages/ps-config-domains.adoc --- cloudhub-2/modules/ROOT/pages/ps-config-domains.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/cloudhub-2/modules/ROOT/pages/ps-config-domains.adoc b/cloudhub-2/modules/ROOT/pages/ps-config-domains.adoc index 412068df..d5524c9c 100644 --- a/cloudhub-2/modules/ROOT/pages/ps-config-domains.adoc +++ b/cloudhub-2/modules/ROOT/pages/ps-config-domains.adoc @@ -9,7 +9,7 @@ Each private space includes one TLS context by default (for traffic to `cloudhub The default certificate renews automatically and requires no action from the user. You can create additional TLS contexts as required. -[IMPORTANT] +[NOTE] ==== The default `.cloudhub.io` domain is shared across all customers in a region. Because private spaces from different customers resolve under the same `.cloudhub.io` parent domain, browsers treat them as the same site, and cookies set at that domain scope aren't isolated between customers. From aa027aa7774c6685511ca17aa08cf0225016b36b Mon Sep 17 00:00:00 2001 From: Daniela Merlo Date: Mon, 3 Aug 2026 15:51:38 -0300 Subject: [PATCH 3/3] w-23153656-dev's feedback --- cloudhub-2/modules/ROOT/pages/ps-config-domains.adoc | 9 +++++---- 1 file changed, 5 insertions(+), 4 deletions(-) diff --git a/cloudhub-2/modules/ROOT/pages/ps-config-domains.adoc b/cloudhub-2/modules/ROOT/pages/ps-config-domains.adoc index d5524c9c..fb09040b 100644 --- a/cloudhub-2/modules/ROOT/pages/ps-config-domains.adoc +++ b/cloudhub-2/modules/ROOT/pages/ps-config-domains.adoc @@ -11,11 +11,12 @@ You can create additional TLS contexts as required. [NOTE] ==== -The default `.cloudhub.io` domain is shared across all customers in a region. -Because private spaces from different customers resolve under the same `.cloudhub.io` parent domain, browsers treat them as the same site, and cookies set at that domain scope aren't isolated between customers. +The `cloudhub.io` parent domain is shared across all customers, control planes, and regions. +Because private spaces from different customers resolve under this same parent domain, browsers treat them as the same site. As a result, cookies set at the `cloudhub.io` scope aren't isolated between customers. -Hosting websites or other browser-facing applications isn't a supported use case for the default `cloudhub.io` domain. -To keep browser-facing applications isolated, deploy them to a customer-owned vanity domain by configuring a TLS context with your own domain and DNS records, as described in this topic. +The domain format varies by control plane. For example, applications on the US control plane use `*...cloudhub.io`, while applications on other control planes add a control-plane suffix, such as `*...eu1.cloudhub.io`. For more information, see xref:ch2-deploy-private-space.adoc[]. + +Hosting websites or other browser-facing applications isn't supported for the default `cloudhub.io` domain. To keep browser-facing applications isolated, deploy them to a customer-owned vanity domain by configuring a TLS context with your own domain and DNS records. See <> to create the DNS records, and xref:ch2-networking-guide.adoc#dns-records[DNS Records] for the CloudHub 2.0 DNS record formats. ==== The TLS contexts that you configure for the private space define the domains that are available