Skip to content

use better k8s versions for spaces testing #1087

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
markandersontrocme merged 1 commit into from
Feb 25, 2026
Merged

use better k8s versions for spaces testing #1087

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
15 changes: 12 additions & 3 deletions docs/manuals/spaces/howtos/self-hosted/deployment-reqs.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -4,13 +4,22 @@ sidebar_position: 2
description: Deploy a Space in your production environment.
---

You need a Kubernetes cluster as the hosting environment to run Spaces. You can
install Spaces into any Kubernetes cluster, version v1.25 or later. Upbound
You need a Kubernetes cluster as the hosting environment to run Spaces. Upbound
validates the Spaces software runs on [AWS EKS][aws-eks], [Google Cloud
GKE][google-cloud-gke], and [Microsoft AKS][microsoft-aks]. Upbound recommends
dedicating the Kubernetes cluster for the express purpose of running Spaces as
its sole workload.

## Kubernetes version compatibility

Each Spaces release is tested against specific Kubernetes versions:

| Spaces Version | Tested Kubernetes Versions |
|----------------|----------------------------|
| 1.15 | 1.32, 1.33, 1.34 |
| 1.14 | 1.31, 1.32, 1.33 |
| 1.13 | 1.30, 1.31, 1.32 |

## Deployment requirements

Spaces requires three things:
Expand Down Expand Up @@ -60,7 +69,7 @@ rightsized the memory available in your Spaces cluster.
:::important
Be careful not to conflate `managed resource` with `custom resource definition`.
The former is an "instance" of an external resource in Crossplane, while the
latter defines the API schema of that resource.
latter defines the API schema of that resource.
:::

It's estimated that each custom resource definition consumes ~3 MB of memory.
Expand Down