Versioned spaces

docs/manuals/spaces/concepts/control-planes.md → cloud-spaces-docs/concepts/control-planes.md

@@ -13,6 +13,7 @@ Control planes in Upbound are fully isolated Crossplane control plane instances
 
 This lets users focus on building their APIs and operating their control planes, while Upbound handles the rest. Each control plane has its own dedicated API server connecting users to their control plane.
 
+
 ## Control plane architecture
 
 ![Managed Control Plane Architecture](/img/mcp.png)
@@ -170,7 +171,7 @@ spec:
 
 <TabItem value="Continuous Delivery Engine" label="Continuous Delivery Engine">
 
-For production-grade scenarios, it's recommended you configure your control plane declaratively via Git plus a Continuous Delivery (CD) Engine such as Argo. For guidance on this topic, read [GitOps with control planes][gitops-with-control-planes].
+For production-grade scenarios, it's recommended you configure your control plane declaratively via Git plus a Continuous Delivery (CD) Engine such as Argo. guidance on this topic, read [GitOps with control planes][gitops-with-control-planes].
 
 </TabItem>
 
@@ -202,20 +203,20 @@ Upbound gives users the ability to configure the collection of telemetry (logs,
 <!-- vale on -->
 
 
-[automatic-upgrades]: /manuals/spaces/howtos/auto-upgrade
+[automatic-upgrades]: /cloud-spaces/howtos/auto-upgrade
 [release-notes]: https://github.com/upbound/universal-crossplane/releases
-[control-plane-group]: /manuals/spaces/concepts/groups
-[space]: /manuals/spaces/overview
+[control-plane-group]: /cloud-spaces/concepts/groups
+[space]: /cloud-spaces/overview
 [up-cli]: /reference/cli-reference
 [cli-reference]: /reference/cli-reference
 [up-ctx]: /reference/cli-reference
 [up-ctx-f]: /reference/cli-reference
 [cli-documentation]: /manuals/cli/concepts/contexts
 [upbound-marketplace]: https://marketplace.upbound.io
 [upbound-marketplace-1]: https://marketplace.upbound.io
-[gitops-with-control-planes]: /manuals/spaces/howtos/cloud-spaces/gitops
+[gitops-with-control-planes]: /cloud-spaces/howtos/gitops-on-upbound
 [connect-control-planes-to-external-services]: /manuals/platform/howtos/oidc
-[spaces-documentation]: /manuals/spaces/howtos/secrets-management
-[spaces-documentation-1]: /manuals/spaces/howtos/backup-and-restore
+[spaces-documentation]: /cloud-spaces/howtos/secrets-management
+[spaces-documentation-1]: /cloud-spaces/howtos/backup-and-restore
 [otel]: https://otel.com
-[spaces-documentation-2]: /manuals/spaces/howtos/observability
+[spaces-documentation-2]: /cloud-spaces/howtos/observability

cloud-spaces-docs/concepts/deployment-modes.md

@@ -0,0 +1,53 @@
+---
+title: Deployment Modes
+sidebar_position: 10
+description: Cloud Spaces deployment modes
+---
+
+Upbound Cloud Spaces come in two deployment modes:
+
+- **Cloud Spaces:** Multi-tenant Upbound-hosted, Upbound-managed Space environment. Cloud Spaces provide a typical SaaS experience. All customers have access to Cloud Spaces by default.
+- **[Dedicated Spaces][dedicated-spaces]:** Single-tenant Upbound-hosted, Upbound-managed Space environment. Dedicated Spaces provide a SaaS experience, with additional isolation guarantees that your workloads run in a fully isolated context.
+
+The Upbound platform uses a federated model to connect each Space back to a
+central service called the [Upbound Console][console], which is deployed and
+managed by Upbound.
+
+:::info Looking for self-hosted options?
+For customer-hosted deployments, see the [Self-Hosted Spaces documentation](/spaces/concepts/deployment-modes/).
+Self-Hosted Spaces include Managed Spaces (Upbound-managed, customer-hosted) and
+Self-Hosted Spaces (customer-managed, customer-hosted).
+:::
+
+## Supported clouds
+
+You can use host Upbound Spaces on Amazon Web Services (AWS), Microsoft Azure,
+and Google Cloud Platform (GCP). Regardless of the hosting platform, you can use
+Spaces to deploy control planes that manage the lifecycle of your resources.
+
+## Supported regions
+
+This table lists the cloud service provider regions supported by Upbound.
+
+### GCP
+
+| Region | Location |
+| --- | --- |
+| `us-west-1` | Western US (Oregon)
+| `us-central-1` | Central US (Iowa)
+| `eu-west-3` | Eastern Europe (Frankfurt)
+
+### AWS
+
+| Region | Location |
+| --- | --- |
+| `us-east-1` | Eastern US (Northern Virginia)
+
+### Azure
+
+| Region | Location |
+| --- | --- |
+| `us-east-1` | Eastern US (Iowa)
+
+[dedicated-spaces]: /cloud-spaces/howtos/dedicated-spaces-deployment
+[console]: /manuals/console/upbound-console/

docs/manuals/spaces/concepts/groups.md → cloud-spaces-docs/concepts/groups.md

@@ -109,7 +109,7 @@ Most Kubernetes clusters come with some set of predefined namespaces. Because a
 3. Labeling a Kubernetes namespace with the label `spaces.upbound.io/group=true`
 
 
-[secrets]: /manuals/spaces/howtos/secrets-management
-[backups]: /manuals/spaces/howtos/self-hosted/workload-id/backup-restore-config/
-[space]: /manuals/spaces/overview
+[secrets]: /cloud-spaces/howtos/secrets-management
+[backups]: /cloud-spaces/howtos/backup-and-restore
+[space]: /cloud-spaces/overview
 [upbound-context]: /manuals/cli/concepts/contexts