Spaces are a self-hosting feature of Upbound’s flagship product for platform teams to deploy managed control planes in their self-managed environments. You can install Spaces into any Kubernetes cluster in your own cloud account, on-premises data center, or on the edge. The pricing usage-based and requires an Upbound account and subscription. The billing unit is a Loop.
Billing details
Spaces aren’t connected to Upbound’s global service. To enable proper billing, the Spaces software ships a controller whose responsibility is to collect billing data from your Spaces deployment. The collection and storage of your billing data happens expressly locally within your environment; no data is automatically emitted back to Upbound’s global service. This data gets written to object storage of your choice. AWS, Azure, and GCP are currently supported. The Spaces software exports billing usage software every ~15 seconds.
Spaces customers must periodically provide the billing data to Upbound. Contact your Upbound sales representative to learn more.
Configure billing at install-time
Billing for a Space must be enabled and configured at install-time.
AWS S3
Configure billing to write to an S3 bucket by providing the following values at install-time. Create an S3 bucket if you don’t already have one.
Then, on the cluster where you installed the Spaces software, create a secret in upbound-system. This secret must contain keys AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY. Make sure to replace the values with a key ID and key generated from your AWS account.
kubectl create secret generic billing-credentials -n upbound-system \
--from-literal=AWS_ACCESS_KEY_ID=<ACCESS_KEY_ID> \
--from-literal=AWS_SECRET_ACCESS_KEY=<SECRET_KEY>
Install the Space software, providing the billing details in addition to the other values you must set.
helm -n upbound-system upgrade --install spaces ... \
--set "billing.enabled=true" \
--set "billing.storage.provider=aws" \
--set "billing.storage.aws.region=<BUCKET_REGION>" \
--set "billing.storage.aws.bucket=<BUCKET_NAME>" \
--set "billing.storage.secretRef.name=billing-credentials"
...
up space init ... \
--set "billing.enabled=true" \
--set "billing.storage.provider=aws" \
--set "billing.storage.aws.region=<BUCKET_REGION>" \
--set "billing.storage.aws.bucket=<BUCKET_NAME>" \
--set "billing.storage.secretRef.name=billing-credentials"
...
Azure Blob Storage
Configure billing to write to a blob in Azure by providing the following values at install-time. Create a storage account and container if you don’t already have one.
Then, on the cluster where you installed the Spaces software, create a secret in upbound-system. This secret must contain keys AZURE_TENANT_ID, AZURE_CLIENT_ID, and AZURE_CLIENT_SECRET. Make sure to replace the values with details generated from your Azure account.
kubectl create secret generic billing-credentials -n upbound-system \
--from-literal=AZURE_TENANT_ID=<TENANT_ID> \
--from-literal=AZURE_CLIENT_ID=<CLIENT_ID> \
--from-literal=AZURE_CLIENT_SECRET=<CLIENT_SECRET>
Install the Space software, providing the billing details in addition to the other values you must set.
helm -n upbound-system upgrade --install spaces ... \
--set "billing.enabled=true" \
--set "billing.storage.provider=azure" \
--set "billing.storage.azure.storageAccount=<STORAGE_ACCOUNT>" \
--set "billing.storage.azure.container=<CONTAINER_NAME>" \
--set "billing.storage.secretRef.name=billing-credentials"
...
up space init ... \
--set "billing.enabled=true" \
--set "billing.storage.provider=azure" \
--set "billing.storage.azure.storageAccount=<STORAGE_ACCOUNT>" \
--set "billing.storage.azure.container=<CONTAINER_NAME>" \
--set "billing.storage.secretRef.name=billing-credentials"
...
GCP Cloud Storage Buckets
Configure billing to write to a Cloud Storage bucket in GCP by providing the following values at install-time. Create a bucket if you don’t already have one.
Then, on the cluster where you installed the Spaces software, create a secret in upbound-system. This secret must contain the key google_application_credentials. Make sure to replace the value with a GCP service account key JSON generated from your GCP account.
kubectl create secret generic billing-credentials -n upbound-system \
--from-literal=google_application_credentials=<SERVICE_ACCOUNT_KEY_JSON>
Install the Space software, providing the billing details in addition to the other values you must set.
helm -n upbound-system upgrade --install spaces ... \
--set "billing.enabled=true" \
--set "billing.storage.provider=gcp" \
--set "billing.storage.gcp.bucket=<BUCKET_NAME>" \
--set "billing.storage.secretRef.name=billing-credentials"
...
up space init ... \
--set "billing.enabled=true" \
--set "billing.storage.provider=gcp" \
--set "billing.storage.gcp.bucket=<BUCKET_NAME>" \
--set "billing.storage.secretRef.name=billing-credentials"
...
Export billing data to send to Upbound
To prepare the billing data to send to Upbound, do the following:
Ensure the current context of your kubeconfig points at the Spaces cluster. Then, run the export command. The example below exports billing data previously stored in AWS:
up space billing export --provider=aws \
--bucket=spaces-billing-bucket \
--account=acmeco \
--billing-month=2024-07 \
--force-incomplete
The command creates a billing report that’s zipped up in your current working directory. Send the output to your Upbound sales representative.
You can find full instructions and command options in the up CLI reference docs.
