Do you touch our workloads or data?
Your pods run on your servers and your data stays there. The control plane can reach your nodes for things like kubectl exec and logs, as any control plane does, so on our side that access is limited to on-call engineers and every session is recorded.
What do our servers need?
Linux with containerd or CRI-O, plus kubeadm and kubelet. They only need to reach your cluster’s endpoint on port 6443. Nothing has to reach in.
Why not run kubeadm ourselves?
You can, and the commands on your nodes would be the same. What you’d be signing up for is everything behind the endpoint: etcd across three zones, backups, certificates, upgrades and the pager. That’s the part we take on.
How is this different from EKS Hybrid Nodes or Azure Arc?
They bill for every vCPU you connect, and they work best if you already live in their cloud. We charge per cluster, and the only thing you adopt is upstream Kubernetes.
Is there a limit on servers?
We don’t count them. The control plane grows as your cluster does. If you’re running something very large or spiky, the Performance tier gives you more room from day one.
Do we need 24/7 on-call?
Only if an outage can’t wait until morning. Standard comes with email support in business hours, and the control plane recovers from most failures without anyone stepping in. If you want someone on call, it’s $200 a month for your whole organization.
We’re a hosting provider. How does partnering work?
You offer managed Kubernetes to your customers and we run the control planes behind it. The customer and the server revenue stay with you, and you pay us a wholesale price per cluster. It all works through our API, so it can live in your own portal.
Who at Kestrel can access our cluster?
Only our on-call engineers, through a break-glass process that’s recorded and open to your review. Nobody keeps standing admin credentials.