What's the difference to a well established tool like kops (https://github.com/kubernetes/kops), which also supports Hetzner?
In Show HN: Edka – Kubernetes clusters on your own Hetzner accountkubernetes
kops
Go2016–2025
kubernetes / kops
kops
Kubernetes Operations (kOps) - Production Grade k8s Installation, Upgrades and Management
41Distinct people
42Mentions
1Explicit recommenders
16.7KGitHub stars
What to know before exploring
What it is
Kubernetes Operations (kOps) - Production Grade k8s Installation, Upgrades and Management
GitHub
Where it is used
No documented product use was verified in the last source check.
What people are saying
I highly recommend the kops[1] tool from Kubernetes if opting to deploy/manage Kubernetes yourself. I’ve had great experiences with it in the past (have been using since before…
koprulusector used a recommendation phrase. One indexed comment matches. This is a phrase match, not a verdict.
No classified warning is attached to this page. Read the discussions before treating silence as approval.
Also in these discussions
No other repository is repeatedly linked in the same discussions.
This week on Hacker News
Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 3:03:16 PM UTC.
No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.
Mentions over time
HN mentions by year42 dated mentions
Observed mentions: 2016-08-20 01:24:18 UTC to 2025-08-15 18:22:55 UTC.
Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.
View mention counts and date ranges
| Period | Start (UTC) | End (exclusive, UTC) | Mentions | Submissions | Comments |
|---|---|---|---|---|---|
| 2016 | 2016-01-01 00:00:00 UTC | 2017-01-01 00:00:00 UTC | 6 | 0 | 6 |
| 2017 | 2017-01-01 00:00:00 UTC | 2018-01-01 00:00:00 UTC | 18 | 3 | 15 |
| 2018 | 2018-01-01 00:00:00 UTC | 2019-01-01 00:00:00 UTC | 10 | 0 | 10 |
| 2019 | 2019-01-01 00:00:00 UTC | 2020-01-01 00:00:00 UTC | 3 | 1 | 2 |
| 2020 | 2020-01-01 00:00:00 UTC | 2021-01-01 00:00:00 UTC | 1 | 1 | 0 |
| 2021 | 2021-01-01 00:00:00 UTC | 2022-01-01 00:00:00 UTC | 1 | 1 | 0 |
| 2022 | 2022-01-01 00:00:00 UTC | 2023-01-01 00:00:00 UTC | 1 | 0 | 1 |
| 2023 | 2023-01-01 00:00:00 UTC | 2024-01-01 00:00:00 UTC | 0 | 0 | 0 |
| 2024 | 2024-01-01 00:00:00 UTC | 2025-01-01 00:00:00 UTC | 0 | 0 | 0 |
| 2025 | 2025-01-01 00:00:00 UTC | 2026-01-01 00:00:00 UTC | 2 | 0 | 2 |
From the project README
An excerpt from the repository, fetched Nov 13, 2026.
Read the project’s introduction
kOps - Kubernetes Operations
The easiest way to get a production grade Kubernetes cluster up and running.
What is kOps?
We like to think of it as kubectl for clusters.
kops will not only help you create, destroy, upgrade and maintain production-grade, highly
available, Kubernetes cluster, but it will also provision the necessary cloud infrastructure.
AWS (Amazon Web Services) and GCP (Google Cloud Platform) are currently officially supported, with DigitalOcean, Hetzner and OpenStack in beta support, and Azure in alpha.
Can I see it in action?
Installing and launching a Kubernetes cluster hosted on AWS, GCE, DigitalOcean, Hetzner, OpenStack, Azure
See Getting Started
Documentation
Documentation is in the /docs directory, and can be seen at kops.sigs.k8s.io.
Releases and kubernetes Release Compatibility
See Releases and versioning
Getting Involved and Contributing
See Contributing
Office Hours
kOps maintainers set aside one hour every other week for public office hours. This time is used to gather with community members interested in kOps. This session is open to both developers and users.
We do maintain an agenda and stick to it as much as possible. If you want to hold the floor, put your item in this doc. Bullet/note form is fine. Even if your topic gets in late, we do our best to cover it.
For more information about the office hours and how to join, see Office Hours
Read the full README on GitHubWhat Hacker News says
42 sourcesAny chance this is the root being that so many different services are effected? https://github.com/kubernetes/kops/issues/17433
In GCP OutageI highly recommend the kops[1] tool from Kubernetes if opting to deploy/manage Kubernetes yourself. I’ve had great experiences with it in the past (have been using since before EKS or Fargate existed).
kops let’s you define your Kubernetes cluster in yaml, then can deploy directly or output terraform that you can use to deploy.
1. https://github.com/kubernetes/kops
In Don't use Kubernetes yetHow does Keights compare to Kops ? https://github.com/kubernetes/kops
In Kubernetes 1.14 releasedHow's this better than kops? https://github.com/kubernetes/kops
In Cheap Kubernetes Cluster on AWS with Kubeadmhttps://github.com/kelseyhightower/kubernetes-the-hard-way
https://github.com/kubernetes/kops
Be aware of this bug at scale ... its interesting
https://blog.quentin-machu.fr/2018/06/24/5-15s-dns-lookups-o...
In Kubernetes for personal projects? No thanksWhats the difference between this and KOPS?
https://github.com/kubernetes/kops
In Knative – Kubernetes-based platform to manage modern serverless workloadsThanks, and yes, I did read through that page. Lots of coloured text that tantalisingly looked like links but weren't, and a lot of broken images/slides.
I got to https://github.com/kubernetes/kops ... and that's where I got out of my depth.
It sounds like it wasn't a problem with YAML per se, but their misappropriation of text/template and wrangling YAML to be something other than a configuration tool. It feels similar to if I were to complain about the shortcomings & complexity of the jinja2 constructs I make within my YAML.
In No: Body: Wants: To: Write: – YAMLI've been so excited for experimenting with EKS ever since the announcement but this offering looks very underwhelming.
With kops [0] I can spin up a production cluster on AWS quickly and have just as much functionality (if not more control) without paying Amazon ~$150/mo for the pleasure (per cluster!). It doesn't really seem to be "managed" either.
Maybe now's the time to really start to look at GCP/GKE. I've used them for some GitLab CI stuff in the past but never invested too much time into really seeing how the transition from AWS to GCP is.
[0]: https://github.com/kubernetes/kops
In Amazon EKS – Now Generally AvailableIt should do - in theory - it needs testing though ;).
I notice that kops recently added support for Digital Ocean
https://github.com/kubernetes/kops/blob/master/docs/tutorial...
So we should be able to add a command `jx create cluster do` for using kops on DO - the current `jx create cluster aws` uses kops under the covers to spin up the kubernetes cluster.
I’ve raised this issue to track it: https://github.com/jenkins-x/jx/issues/705
In Jenkins X: a CI/CD solution for cloud applications on KubernetesKubernetes and Nomad are resource schedulers. Resource scheduling is a hard problem. For example, Linux is also a resource scheduler.
Right now, we're seeing something similar to the OS wars in the 80's, 90's and 2000's. Back then there was Solaris, Linux, Unix, BSD, etc. In the 2000's, Linux won. After that, the sheer force of community made it easy to deploy and use.
The community around Linux mitigated its complexity by making distributions -- opinionated choices around how to set up linux, including what package manager to use, what init process to use, etc.
Kubernetes is, in my opinion, far more complicated than Nomad, but it's also more feature rich. To mitigate that complexity, quasi-distributions of kubernetes are emerging, like kops ( https://github.com/kubernetes/kops ) and kubespray ( https://github.com/kubernetes-incubator/kub
Read the rest
espray ). My personal favorite is Typhoon ( https://typhoon.psdn.io/ ), because it uses a "package manager" (software delivery mechanism) that allows you to declare dependencies between packages and also allows you to deploy the entire cluster from the ground up -- Hashicorp's Terraform ( https://www.terraform.io/ ).
The kubernetes package manager is helm ( https://helm.sh/ ), but if I were you I'd wrap helm charts in terraform modules using the helm provider ( https://github.com/mcuadros/terraform-provider-helm ).
By contrast, Nomad is much simpler to set up and has a much better modular design. But then, so did the OS GNU Hurd. And no one uses that anymore. Kubernetes is much more monolithic in design (huh, so is Linux).
Therefore, I would choose kubernetes, but treat it like an OS. It's complicated. Don't choose what ingress you will use. Instead choose what distribution you will use, and let the distribution guide your decisions, unless you have a good reason.
Realize that you're learning an OS (resource scheduler = os in my head). Kubernetes has more complexity than Nomad up front, but at least it's not accidental complexity. K8s calls the resource scheduler problem what it is -- hard, and treats it appropriately.
The other safe bet is Terraform as the package manager. Choose a kubernetes distro that uses it (Typhoon, Kops). It is getting huge.
Kubernetes' extensible API is what really makes it cool. Having a prometheus operator ( https://github.com/coreos/prometheus-operator ) automatically monitor your services for you is pretty nice.
Finally, don't expect the stability you see in the Linux OS. Kubernetes is still coming out of the primordial ooze, though it's way more mature than Nomad in its community. Still, when a google search for how to do something on a cluster mostly turns up github issues, you know we're still in the early stages.
That said, Nomad is way easier to set up, and supports things like raw execution, JVM direct execution, and chrooted exec, so if you can't use containers at least you can still use a cluster. You'll be rigging everything yourself, but raw execution actually gives you a lot of rope ( https://github.com/hashicorp/nomad/issues/150 ). So if you need to do something really custom, Nomad might not be so bad. Kind of like embedded Linux.
Showing the 15 most recent of 42 sources. Enable JavaScript to search and browse every indexed mention.