Re:Container technologies at Coinbase: Why Kubernetes is not...
by mpfundstein on Monday June 08, 2020 @05:18PM
(#23460923)
Nomad, Consul + Swarm is still a lovely solution and I prefer it a lot to K8s. K8s is a big monolith and often way too complex for my personal use cases.
I hope Hashicorp sooner or later builds a proper replacement for Swarm so that we can have overlay networks without hassle. I know there is Weave, but never tried it.
[ Parent
| on HN ]
Re:Container technologies at Coinbase: Why Kubernetes is not...
by tie_ on Monday June 08, 2020 @05:56PM
(#23461253)
K8s is a lot of things, but a monolith it is not. Quite the opposite - the complexity comes from the large number of relatively simple components interacting in various ways.
Re:Container technologies at Coinbase: Why Kubernetes is not...
by kitotik on Monday June 08, 2020 @05:55PM
(#23461240)
Which part of Swarm are you looking to replace?
Nomad already does the container part, and Consul Connect is the networking overlay / service mesh. Work is being done to get Nomad better integrated with Connect.
Re:Container technologies at Coinbase: Why Kubernetes is not...
by schmichael on Monday June 08, 2020 @09:40PM
(#23462767)
Broader CNI and multi-interface networking support coming in 0.12!
Would love to hear what else you miss from swarm: [email protected]
Update: Honestly if you haven't tried out our Consul Connect integration, please do. mTLS with just "connect { sidecar_proxy {} }" stanza and Consul running: https://www.nomadproject.io/docs/integrations/consul-connect...