Kubernetes¶
Wodby supports four practical deployment choices for Kubernetes-backed applications.
Use these pages when you are deciding where your app should run or when you need to connect or create a cluster.
Quick comparison¶
| Option | Best when | Created from |
|---|---|---|
| Managed Kubernetes | You want cloud-native infrastructure in your own provider account | Kubernetes |
| K3S | You want self-hosted Kubernetes on your own server | Kubernetes > Connect server |
| Wodby Cloud | You want Wodby to create and manage the cluster | Kubernetes > New Wodby Cloud cluster or Apps > New app > Step 2 |
| Demo | You want a temporary test cluster for 24 hours | Kubernetes > New Wodby Cloud cluster > Demo or Apps > New app > Step 2 > Wodby Cloud > Demo |
See Choose a Kubernetes option for the full decision guide.
1. Managed Kubernetes¶
Ready-to-run, scalable clusters created in your own cloud account through integrations such as GCP, AWS, Azure, DigitalOcean, and OVH.
If you plan to scale your cluster and need more flexibility, we recommend this approach.
Create these clusters from the Kubernetes section after connecting the corresponding provider integration.
2. Self-hosted Kubernetes with K3S¶
If you want to save money and have more control over your cluster, you can deploy a self-hosted Kubernetes cluster using K3S.
Connect your server from the Kubernetes section using the Connect server flow.
3. Wodby Cloud¶
If you want Wodby to create and manage the cluster for you, create it from Kubernetes > New Wodby Cloud cluster or choose Wodby Cloud in Step 2 of the new application form.
Persistent Wodby Cloud clusters require a paid plan.
Demo¶
Demo is the temporary Wodby Cloud option for testing. Enable the Demo switch when creating a Wodby Cloud cluster from the Kubernetes page or from the new application flow.
Demo clusters are deleted automatically after 24 hours. Applications deployed to a demo cluster are deleted with it.