In short: CAPVCO turns a few lines of YAML into a production-grade Kubernetes cluster on whitesky.cloud. You describe the cluster you want; a controller builds and continuously reconciles everything underneath it: cloudspaces, VMs, disks, load balancers, DNS and storage.
What you get out of the box
It is not a thin “boot some VMs and run kubeadm” provider. The hard, safety-critical parts of running clusters are included and reconciled:
- Geo-redundant control plane: one logical cluster stretched across multiple cloudspaces and datacenters, meshed over an automatically built site-to-site VPN.
- Tested etcd backup and restore: hourly encrypted snapshots to S3 / objectspaces with Object Lock, and a restore path that has actually been exercised.
- Storage, including encrypted: the whitesky.cloud CSI driver with online volume expansion and LUKS2 at-rest encryption backed by Vault or OpenBao.
- ExternalDNS and load balancers:
Service type=LoadBalancergets a real external IP, and hostnames are published to whitesky.cloud-managed DNS automatically. - Air-gapped clusters: no public-internet egress needed; an in-cloudspace registry serves every image locally.
- Day-2 on autopilot: rolling upgrades, self-remediation, certificate and credential rotation, disk auto-growth and drift cleanup.
Works with any whitesky.cloud portal
CAPVCO is white-label generic: the portal URL, IAM endpoint, customer ID and credentials are deployment configuration, so the same build works against any whitesky.cloud portal, including partner-branded ones. New to the model behind it? See the Cloud Enabler / VCO model.
License
CAPVCO is released under the Apache License 2.0, and the source code is public.
Contribute
Want to contribute, report an issue or discuss a use case? Get in touch and we’ll connect you with the team.