Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Devops/arch here, I think Kubernetes solves deployment in a standardized way and we get fresh clean state with every app deploy. Plus it restarts applications/pods that crashes.

That said I think Kubernetes may be at its Productivity journey on the tech Hype cycle. Networking in Kubernetes is complicated. This complication and abstraction has a point if you are a company at Google scale. Most shops are not Google scale and do not need that level of scalability. The network abstraction has its price in complexity when doing diagnostics.

You could solve networking differently than in Kubernetes with IPv6. There is not a need for complicated IPv4 nat schemes. You could use native ipv6 addresses that are reachable directly from the internet. Since you have so many ipv6 addresses you do not need Routers/Nats.

Anyhow in a few years time some might be using something simpler like an open source like Heroku. If you could bin pack the services / intercommunication on the same nodes there would be speed gains from not having todo network hops going straight to local memory. Or something like a standardized server less open source function runner.

https://en.wikipedia.org/wiki/KISS_principle https://en.wikipedia.org/wiki/Hype_cycle



This is a good point, I was wondering why IPv6 is being avoided so hard.

There are many arguments that IPv6 didn't solve too many IPv4 pain points, but if it solved something is definitively this.


Good point on the app restart. I think K8S is in some ways the equivalent of Erlang BEAM for the masses for the cloud.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: