Skip to content

Versioned spaces#1070

Draft
tr0njavolta wants to merge 11 commits intomainfrom
versioned-spaces
Draft

Versioned spaces#1070
tr0njavolta wants to merge 11 commits intomainfrom
versioned-spaces

Conversation

@tr0njavolta
Copy link
Member

@tr0njavolta tr0njavolta commented Jan 29, 2026

Description

#1029
This PR attempts to address the issue of Spaces versioning. This creates a multi-site instance for the Spaces docs to avoid confusion with UXP versioning.

The multi-site implementation is in line with what Docusaurus recommends for distinct sets docs (UXP vs Spaces in this case) https://docusaurus.io/docs/docs-multi-instance

Type of change

  • Bug fix (typo, broken link, incorrect info)
  • Content update (new info, clarification, reorganization)
  • New content (new page, section, or guide)

Checklist

  • I ran make lint locally (or will fix Vale suggestions in review)
  • Links work and point to the right places
  • If this adds new content, I tested the examples/instructions

Additional notes

@vercel
Copy link

vercel bot commented Jan 29, 2026

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Review Updated (UTC)
docs Ready Ready Preview, Comment Jan 29, 2026 4:26am

Request Review

@tr0njavolta
Copy link
Member Author

Todo:

  • Breadcrumbs in Spaces site with better navigation back to "Home"

Copy link
Contributor

@cbuto cbuto left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I started going through 1.13 docs and noted somethings I found. Some of it might apply to other versions as well.

I still need to go through more but its a lot 😄

```shell
helm upgrade spaces spaces-helm-chart \
--set "billing.enabled=true" \
--set "backup.enabled=true" \
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

these backup configurations do not exist 🤔

I think this guide is complementary to https://docs.upbound.io/manuals/spaces/howtos/backup-and-restore/#configure-a-shared-backup?


## Shared backups

As of Spaces `v.12.0`, this feature is enabled by default.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

we can prob drop this reference to 1.12 and just state its enabled by default

---

:::important
This feature is in preview. Starting in Spaces `v1.8.0` and later, you must
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

we can drop the references to 1.8

}
```

For more information about workload identities, review the [Workload-identity
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

definitely some overlap with the workload ID doc for billing here. In the future, we should probably combine or maybe even remove https://docs.upbound.io/manuals/spaces/howtos/self-hosted/workload-id/billing-config/

reporting isn't possible.

:::info
Spaces `v1.15` and later support Capacity Licensing as an
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

we can drop this page from 1.13 and 1.14

kubectl describe pod -n <namespace> <pod-name>
```

Next, inspect the status of objects and releases:
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is no longer valid for 1.13 (objects and releases)

<!-- vale off -->
### Your control plane is stuck in a 'creating' state

#### Error: unknown field "ports" in io.k8s.api.networking.v1.NetworkPolicySpec
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

we can drop this tip from all versions


#### Error: You tried to install a Space on a previous Crossplane installation

If you try to install a Space on an existing cluster that previously had Crossplane or UXP on it, you may encounter errors. Due to how the Spaces installer tests for the presence of UXP, it may detect orphaned CRDs that weren't cleaned up by the previous uninstall of Crossplane. You may need to manually [remove old Crossplane CRDs][remove-old-crossplane-crds] for the installer to properly detect the UXP prerequisite.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is no longer valid, Spaces doesn't require UXP and doesn't install it


Spaces supports the three [preceding minor versions][preceding-minor-versions] from the last supported minor version. example, if the last supported minor version is `1.14`, minor versions `1.13` and `1.12` are also supported. Versions older than the three most recent minor versions aren't supported. Only supported Crossplane versions are valid specifications for new control planes.

Current Crossplane version support by Spaces version:
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

oh man this is out of date lol, maybe we just drop this in all docs versions

Once the control plane is ready, connect to it.

```bash
up ctp connect my-control-plane
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

up ctp connect was superseded by up ctx commands

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants