Had been 5 months and the new hashicorp's code has been changed (bugfixes, etc) and as the drift from the last opensource code becomes wider (even worst, a major change with major versions), i'm setup an organisation for the community to discuss and help on the future to work on the last opensourced version of consul and nomad.
My organisation depends a lot on consul and nomad and the BSL makes it unnecessarily complicated for our case.
https://github.com/OpenHotPot/OpenHotPot (Consul) https://github.com/OpenHotPot/OpenNood (Nomad)
The only “kinda cool”, thing I saw with Nomad is that it can “orchestrate” binary files, not just containers.
That said, putting binaries in containers isn’t very difficult.
I've also heard that the fuck-you license change was actually a negotiation tactic for the acquisition
* https://github.com/hashicorp/nomad/forks
* https://github.com/search?q=nomad%20fork&type=repositories
* https://www.google.com/search?q=hashicorp+nomad+forks
There are products that do similar things of course.
There are still some rough edges but it's been a decent secret store for my small team doing mostly Docker Compose/bare metal stuff.
I'm curious to hear if any other people have managed to use open OR closed-source source password managers as Vault/Consul replacements.
It keeps secrets out of your environment variables and lets you manage secrets the same way you do code (in lock-step with the code that uses it and as easy to update a secret just by pushing to git), but it's definitely for smaller teams or projects. It also has significantly fewer moving parts or dependencies.
There's always Zookeeper.
I hate etcd with the best of them, but etcd is used in a lot more places than just kubernetes:
https://github.com/apache/apisix/blob/master/docs/en/latest/...
https://github.com/traefik/traefik#:~:text=Etcd,
https://github.com/zalando/patroni#patroni-a-template-for-po...
https://github.com/purpleidea/mgmt/tree/0.0.26/etcd (this one shows up on HN quite a bit)
https://github.com/sorintlab/stolon#features
It's actually one of the major reasons I wouldn't touch those projects
I really love Nomad's UX, so I hope we get one sometime soon-ish.
I know neither of them are as nicely opinioned at those two services but there is starting to be plenty of more opinioned Kubernetes deployments.
k3s is probably most well known as it ships with bunch of preinstall software: https://github.com/k3s-io/k3s so you can just start throwing yaml files at cluster and handling workloads. It's what I use for my homelab.
Paid things I've heard of include OpenStack and SideroLabs. Haven't used personally by SRE coworkers say good things about them.
As SRE who deals with a ton of Kubernetes clusters, I find a ton of needlessly complex clusters because rookies setting up the clusters didn't understand the implications of their actions and grabbed whatever a blog post said was good idea.
Learned about it in this blog post: https://fly.io/blog/building-clusters-with-serf/
I'm confused. Isn't that what consul originally was?
