Pure upstream Kubernetes. No forks, no proprietary 'improvements', no 3am tears. Just a control plane that doesn't fall over and a regular kubectl.
Most managed-Kubernetes offerings collapse into one of two camps: either a two-year-old fork with holes in RBAC, or a 'wrapper' with a murky API and its own CLI. We went a different way.
Via our CLI or Terraform — pick whichever fits. No web-only, no 'click the button'.
# create a 1.31 cluster on 3 nodes in moscow $ h3llo k8s create hyperion-prod \ --version 1.31 \ --region msk-a \ --nodes 3:s2.standard \ --addons ingress,cert,metrics # in about 4 minutes: cluster hyperion-prod is ready kubeconfig saved to ~/.kube/config $ kubectl get nodes node-01 Ready Master,Worker 8 vCPU node-02 Ready Worker 8 vCPU node-03 Ready Worker 8 vCPU
terraform { required_providers { h3llo = { source = "h3llo/h3llo" version = "~> 0.4" } } } resource "h3llo_k8s_cluster" "prod" { name = "hyperion-prod" version = "1.31" region = "msk-a" node_pool { name = "default" type = "s2.standard" min_size = 3 max_size = 12 } }
Tweak the knobs — see what the cluster looks like and what it costs. Then hit 'Create' and 4 minutes later you have a kubeconfig.
The control plane is always free, no matter how many clusters you run. You pay for what actually burns resources — the worker nodes.
No fluff, no marketing. Real practice from our SREs and architects — grab the PDF, read it over the weekend, ship it on Monday.
RBAC, network policies, PDBs, limits, etcd backups, observability — what you must verify before release.
Right-sizing, spot nodes, HPA/VPA done right, pool separation, unused-capacity monitoring. With formulas and Grafana dashboards.
Inside the migration of 86 microservices: what broke, what got simpler, numbers before/after. No sugar-coating.
Pod Security Admission, network policies, image scanning, secrets management. What to ship now, what to ship in Q2.
Llama 3.1 70B, Qwen 2.5, tokens/sec, cost per 1M tokens. Numbers from our hardware, not from marketing slides.
Production-ready modules: cluster, node-pools, ingress, monitoring. With examples for dev/staging/prod environments.
If our CLI is already installed — skip to step 3. If not — here's the full path.
Let's go →brew install h3llo/tap/cli · or curl get.h3llo.cloud | shh3llo auth login — the browser opens for you, the token is stored locally.h3llo k8s create my-cluster --nodes 3:s2.standard · ~4 minutes and you have a kubeconfig.kubectl apply -f . — it's just Kubernetes. No new concepts.Sign up by email. No card required. 4,000 ₽ already on your balance — enough to spin up a couple of test clusters for a whole month.