Is this a real managed Kubernetes service, or a script that installs it on my server?
Managed. We run the control plane, including etcd and its snapshots, and we drive the upgrades when you start one. Your dedicated servers join the cluster as worker nodes, and you never have to operate the control plane yourself.
Which Kubernetes distribution do you use?
RKE2, a CNCF-conformant distribution that ships upstream Kubernetes. Your manifests, Helm charts and operators work as they would on any other conformant cluster.
Do I keep root access to the worker nodes?
Yes. Each worker is a dedicated server on your account, with root SSH, the console and rescue mode, exactly as when it is not part of a cluster. That is the main difference from most managed Kubernetes, where the nodes are often closed to you.
How many nodes does a cluster need?
One control-plane node is the development tier: a single API server and a single etcd, so a reboot or an upgrade takes the cluster's API with it. Three is the highly available tier, where etcd keeps quorum while one of them is down. On the worker side one server is enough to run pods; two or more is what lets a workload with several replicas keep serving while one node is upgraded, since the nodes go one at a time. The machines a worker can be are on the dedicated servers page.
How do Services of type LoadBalancer get an IP address?
MetalLB assigns them the extra IPv4 addresses on your worker servers, so the address in front of your Service is one you already hold rather than one we lend from a shared pool.
Can I run my own ingress controller?
Yes, the choice is yours. With cluster-admin you deploy or configure ingress-nginx, Traefik or another controller from its Helm chart and expose it through a Service of type LoadBalancer, which MetalLB puts on one of your workers' extra IPv4 addresses. That address is what your DNS points at, and the TLS certificates are yours to issue, with cert-manager or whatever your pipeline already uses.
Do the nodes share a private network?
No, there is no private VLAN per cluster. The nodes reach each other over their public addresses on our network, and a firewall on every node admits only the cluster's own nodes. Traffic between nodes is not encrypted by the cluster: Cilium network policies control which pods may talk, and for encrypted traffic between services use TLS or mTLS in your applications, or a service mesh.
Can one cluster mix GPU and CPU servers?
Yes. You pick each worker server from the New York machines ready now, so GPU and CPU servers can join the same cluster. They all start in one pool labelled pool=general; with cluster-admin you label and taint the GPU nodes yourself, and workloads choose between them with node selectors and tolerations.
How are upgrades done?
You choose when. We upgrade the control plane first, then the worker nodes one at a time, so a workload running more than one replica keeps serving while the cluster moves to the new version.
Is it available now, and where?
Yes, in New York. On the order page you choose a Dev or HA control plane and one to ten worker servers from the New York machines ready now; the cluster is built once the first invoices are paid, and its kubeconfig waits in your dashboard.