by Thierry de Pauw on
Nomad doesn't seem
I have problems with Kubernetes. I've used it and had even more problems with it.
- I don't like non-essential complexity
required complexity is what you need to fulfil a business need
From how I see it: K8s is accidental complexity. @Pondidum
Cindy Sridharan @copyconstruct
Docker succeeded not because of “the tech” (containers) but because it was a great developer tool.
Kubernetes built atop Docker, and decided to be all things tech and not much by way of UX. It was and remains a hostile piece of software to learn, run, operate, maintain.
If you are going to use K8s, please use a cloud service. @Pondidum
Don't waste time managing K8s.
Nomad comes with one binary: cli + server mode @Pondidum
- server mode
- health checks
- container management
- storage orchestration
- rollouts & rollbacks
Nomad: No YAML! This is the best reason for not using Kubernetes. @Pondidum
cpu: 500 #Mhz instead of .2 of cpu
memory: 256 #Mb
Nomad assigns a job version and checks for that at deploy time
anyone had problems with Helm state? runtime state different from Helm known state
Kubernetes secrets are not secret. They are obfuscated.
... secret data is stored in ectd; therefore: Administrators should limit access to etcd.
Nomad uses Vault
Vault supports AWS IAM, Github authentication, Active Directory
as fas as I know Kubernetes can only run docker containers
Nomad can run any binary: exec, Java, Docker, Qemu
- artefact can be fetched via HTTP packaged as an archive
downside: you lose the isolation that docker gives you
use case: .NET application, small size, can only be run in K8s using a Windows Docker image that is several Gb big => run as executable in Nomad
there are several ones, I use always the default one
Nomad has the feature of "affinities": these nodes support .NET, these not