Before you start
The platform is multi-tenant: customers share a control plane but have their own dedicated worker nodes. If that is not the right fit, we can set up a dedicated platform for you.
Here is what is good to know to get the most out of the platform.
Design for high availability
Maintenance, reboots and other events can happen at any time, and your application should be able to handle them without downtime. This applies to all Kubernetes clusters, but is especially worth keeping in mind on a multi-tenant platform. See Best practices for how to get there.
Permissions are limited to your namespaces
Cluster-wide permissions through cluster roles/rolebindings are not available, and neither is installing your own operators. If you need either, a dedicated platform may be a better fit, so get in touch and we will find a good solution together.
Use git for restores
We do not restore single Kubernetes objects, so we recommend keeping everything in git and using a GitOps tool like ArgoCD. That way you can restore whenever you need to. Secrets can be stored safely in git using encryption, see Secrets with KSOPS.
Plan backups of persistent data
Data created by Kubernetes objects, such as persistent volumes, is not covered by git. Make sure you have a backup plan for it. See Persistent storage.