Kubernetes runs and manages containers across a group of servers. It restarts containers that crash, spreads them across nodes, rolls out new versions without downtime, and scales them up under load. Doing all of that by hand is a lot of work, so Gewape Cloud runs the control plane and the servers for you. You get a standard, conformant Kubernetes cluster that you drive with the usual kubectl tool, so anything written for Kubernetes works here unchanged.
You manage clusters under Kubernetes in the console.
The pieces
- A cluster template defines the shape of a cluster: the Kubernetes version, the node size, and networking. You can reuse a template for many clusters.
- A cluster is created from a template. It has control-plane nodes (which run Kubernetes itself) and worker nodes (which run your containers).
- A kubeconfig file authenticates
kubectlto your cluster.
When to use it, and when not
Kubernetes is aimed at teams that package their applications as containers and want automated deployment, scaling and recovery. If you are running a single website or app, a Cloud Server is simpler and cheaper. Reach for Kubernetes when you have several services, need zero-downtime deploys, or want to scale parts of your system independently.
How to
A cluster runs on real servers, so it draws from your wallet for as long as it exists. Delete clusters you are only testing.