3 ms·
Sigh. More “Kubernetes == Containers” words to throw on the pile. It’s easy to find issues/point at problems with the post, but I’m happy the author is suggesti
by amerine 5y ago
Sigh. More “Kubernetes == Containers” words to throw on the pile. It’s easy to find issues/point at problems with the post, but I’m happy the author is suggesting long-term view of your system and is making a suggestion that k8s could help, that may be true along some slices, but you are biting off learning a complexity you may not be ready for.
- throwaway894345 5y ago> but you are biting off learning a complexity you may not be ready for. I really think people forget how complex it is to manage VMs in any sort of reliable, reproducible fashion. In my opinion, there's a lot more complexity in configuring your process management, SSH, key management, host metrics, log exfiltration, reverse proxy, etc than there is in using a managed Kubernetes offering like EKS or GKE. You end up reinventing a lot of things with VMs to get to a state that these managed Kubernetes services give you out of the box. This doesn't diminish the complexity of using Kubernetes, but the "simpler alternative" is something like Heroku, not EC2 (to be clear, you didn't advocate for EC2, I'm rebutting the predictable, popular argument).
- wlpu 5y agoI hope one day people realise there is a place other than kubernetes and VMs to run containers, such as GCP's Cloud Run or AWS's ECS Fargate, these are essentially plug container and play services which avoid the baggage of kubernetes and VMs
- throwaway894345 5y agoYeah, although I get the feeling that at least ECS/Fargate will fall behind EKS as the EKS ecosystem matures (not so sure about the GCP world).