Get started with Upbound Spaces. This guide deploys a self-hosted Upbound cluster with a local kind
cluster.
Disconnected Spaces allows you to host managed control planes in your preferred environment.
Prerequisites
To get started deploying your own Disconnected Space, you need:
- An Upbound Account string, provided by your Upbound account representative
- A
token.json
license, provided by your Upbound account representative kind
installed locally
Provision the hosting environment
Upbound Spaces requires a cloud Kubernetes or kind
cluster as a hosting environment. For your first time set up or a development environment, Upbound recommends starting with a kind
cluster.
Create a cluster
Provision a new kind cluster.
cat <<EOF | kind create cluster --wait 5m --config=-
kind: Cluster
apiVersion: kind.x-k8s.io/v1alpha4
nodes:
- role: control-plane
kubeadmConfigPatches:
- |
kind: InitConfiguration
nodeRegistration:
kubeletExtraArgs:
node-labels: "ingress-ready=true"
extraPortMappings:
- containerPort: 443
hostPort: 443
protocol: TCP
EOF
Configure the pre-install
Set your Upbound organization account details
Set your Upbound organization account string as an environment variable for use in future steps
export UPBOUND_ACCOUNT=
Set up pre-install configurations
Export the path of the license token JSON file provided by your Upbound account representative.
# Change the path to where you saved the token.
export SPACES_TOKEN_PATH=""
Set the version of the Spaces software you want to install.
export SPACES_VERSION=1.7.0
Install the Spaces software
The up CLI gives you a “batteries included” experience. It automatically detects which prerequisites aren’t met and prompts you to install them to move forward. This guide requires CLI version v0.33.0
or newer.
Install the Spaces software.
up space init --token-file="${SPACES_TOKEN_PATH}" "v${SPACES_VERSION}" \
--set "account=${UPBOUND_ACCOUNT}"
You are ready to create your first managed control plane in your Space.
Create your first managed control plane
With your kubeconfig pointed at the Kubernetes cluster where you installed the Upbound Space, create a managed control plane:
up ctp create controlplane1
The first managed control plane you create in a Space takes around 5 minutes to get into a condition=READY
state. To report the control plane status, use the following command:
up ctp list
Connect to your managed control plane
Connect to your managed control plane with the up ctx
command. With your kubeconfig still pointed at the Kubernetes cluster where you installed the Upbound Space, run the following:
up ctx ./default/ctp1
This command updates your current kubecontext. You’re now connected to your managed control plane directly. Confirm this is the case by trying to list the CRDs in your managed control plane:
kubectl get crds
To disconnect from your managed control plane and switch back to your previous context:
up ctx -