Managed Kubernetes in Your Own Cloud Account
When to move from a VPS to managed Kubernetes, which cloud accounts Rubuz supports, and how clusters are billed.
Rubuz starts with a single VPS: git push deploys, databases, SSL and backups on a server you rent. When one server is no longer enough, Rubuz also runs managed Kubernetes clusters in your own cloud account, from the same console.
When to move to Kubernetes
A single VPS is the right place for most apps. Consider a cluster when you need:
- High availability, so the app keeps serving when a node goes down.
- Autoscaling, so the cluster adds capacity when traffic grows.
- Rolling deploys across several nodes.
Your VPS servers and your clusters stay side by side in the same console, so you can keep some apps on a VPS and move others to a cluster.
Supported cloud accounts
Clusters run in your own account with one of these providers:
- DigitalOcean
- Vultr
- Linode
You get high availability, autoscaling and rolling deploys without the cost and complexity of EKS or GKE.
Billing
The cluster belongs to your cloud account, so the nodes are billed to you by your provider, the same way your VPS servers are. Rubuz charges only for the platform.
Getting a cluster set up
Managed Kubernetes is part of the Kubernetes + VPS plan. Talk to us about the clusters you want to run, and we will help you connect your cloud account. You can compare the two plans on the pricing page.