Kubernetes distributes containers across several machines and restarts them after a failure; such a group of machines is called a cluster. Under Connections you store access to your cluster, once for the whole organization like the other connections. The platform keeps the access file encrypted; afterwards the interface only shows that a cluster connection exists. Which permissions this access has inside the cluster remains up to you, because today the platform only checks and stores the file.
Adding the access
- Open Connections and click Add connection.
- Choose the Kubernetes tile.
- Paste your cluster’s access file, the configuration file that tools such as
kubectlalso use to sign in to the cluster, and save.
The platform checks the file and stores it. The access is then available to the whole organization and can later be assigned to projects.
What happens with it today
Applications currently still run with Docker on the server. Rolling them out onto a Kubernetes cluster is the platform’s next step, which is why Kubernetes still appears as coming soon in the server overview. Until then, managed servers, your own server over SSH, and cloud servers at Hetzner or Hostinger remain the ways your applications run. You can still store the access now so that it is in place once deploying to the cluster becomes available.