4 ms·

I think nomad really needs a k3s equivalent. The equivalent of k8s is not nomad, it's nomad+consul+vault If you read through something like kubernetes-the-har

I think nomad really needs a k3s equivalent. The equivalent of k8s is not nomad, it's nomad+consul+vault If you read through something like kubernetes-the-hard-way most of the really tricky parts are setting up the PKI infrastructure and bootstrapping etcd. https://learn.hashicorp.com/tutorials/nomad/security-enable-tls?in=nomad/transport-security https://learn.hashicorp.com/tutorials/nomad/security-enable-... starts to look a lot like https://github.com/kelseyhightower/kubernetes-the-hard-way/blob/master/docs/04-certificate-authority.md https://github.com/kelseyhightower/kubernetes-the-hard-way/b... Vault is better than k8s secrets, but getting nomad working doesn't magically give you a working vault cluster.

steeleduncan 6y ago
> The equivalent of k8s is not nomad, it's nomad+consul+vault This was my stumbling block. Nomad alone is clearly easier than k8s, and if it alone will suit your needs then you are in luck, but I didn't find installing and configuring 3 separate services any easier than k8s alone.
- insanejudge 6y ago
  I've never seen a reliable, scaled and coherent k8s operation without at least vault, and often consul as well, so that argument never held any water for me
- AnxiousCoward 6y ago
  We had to add vault to our setup even if we use kubernetes - kubernetes secrets are a joke. We don't use consul, but managing istio, or any other service mesh, on top of kubernetes, isn't any simpler than running your own consul. (In fact, I have found istio to be a lot more difficult to get to do what you need than consul's service mesh, and with less functionality.)