4 ms·

> k8s on your own bare metal at least used to be not exactly straight forward. I actually just deployed k8s on a raspberry pi cluster on my desk (obviously as

> k8s on your own bare metal at least used to be not exactly straight forward. I actually just deployed k8s on a raspberry pi cluster on my desk (obviously as a toy, not for production) and it took about an hour to get things fully functional minus RBAC. > What I'm saying is that Nomad is a general purpose workload scheduler Yeah, Nomad and k8s are not direct replacements at all. Nomad is a great tool for mixed workloads, but if you're purely k8s then there are more specific tools you can use. > I meant to write 4.4K lines Just a small difference! Glad no one wrote 44k lines of yaml, that's just a lot of yaml to write... > close to 12k lines Our production cluster (not the raspis running on my desk!) runs in about 4k lines, but we have a fairly simple networking and RBAC layer. We also started from just kubernetes and grew organically over time, so I'm sure someone starting today has a lot of advantage to get running more easily.

jordanbeiber 7y ago
If you want ”cloud style” ingress, you’ll probably use metalLB and bgp etc. Here’s where it gets fun. I mean, don’t get me wrong, it works - now at least. Never liked it until 1.12 tbh, which is when a bunch of things settled. The article is about “maybe you don’t need...” and as an anecdote I helped build a really successful $$$ e-commerce business with a couple of hundred micro-services on an on-prem LXC/LXD “cloud” using nomad, vault & consul. You can use these tools independently of each other or have them work together - unixy. I have anecdotes from my last couple of years on k8s as well, and... it just ends up with a much more narrow scope.