4 ms·

If you use a good managed k8s offering, the complexities are not that great. GKE with Autopilot is a good option. In that case you don't need to know much more

If you use a good managed k8s offering, the complexities are not that great. GKE with Autopilot is a good option. In that case you don't need to know much more than how to write the yaml for a deployment. I've shown developers at all levels how to do that, it's not a barrier.

hobofan 4y ago
+1. GKE Autopilot and sticking to the core ~4 Kubernetes object kinds (Deplyoment, Service, Ingress), was a really easy way for us to get started with K8s (and in many cases can carry you a really long way).
- amtamt 4y ago
  Though easy to run, if there are multiple workloads of varying resource requirements, there will be a lots of wasted CPU and RAM, just because there are minimum CPU and CPU to RAM requirements.
- crucialfelix 4y ago
  Agree. I think they are working towards providing ISTIO (gateway replaces ingress, TLS internal communication, canary deployments, shadowing etc). If they can spin up GPU or high memory nodes on demand with Autopilot that would be amazing.
evoxmusic 4y ago
There is also a new generation of platform that runs on top of Kubernetes that are emerging. Like Qovery
tuxie_ 4y ago
Why would you run it in k8s as opposed to, say, ECS? Honest question here, why not run it on something simpler that requires less new concepts and achieves the same results?
- akvadrako 4y ago
  Because ECS sucks. It's slow and unergonomic, like a badly designed k8s with fewer features. k8s is nicer to use and simpler if you ignore the complex bits. Plus it's the standard.
  - kungfufrog 4y ago
    My experience of ECS is the opposite of yours. It integrates nicely with the AWS ecosystem and was substantially easier to use and educate others on. Would not hesitate to use again on either fargate or BYO EC2. I will acknowledge scheduling is not quite as fast as Nomad but I never found it 'slow'
    - ownagefool 4y ago
      Personally, I'd rather create a k8s deployment than an ECS task, but I can see your point. If all you want is an integrated with AWS experience, then it makes som sense that ECS is just simpler overall out of the box. I don't think the delta to make k8s integrated is that much work with EKS, but ability to mutate the entire infrastructe if and when you do scale wins out for me. I think the complexity, most of which you can ignore, is worth the flexibility. Either way, since k8s landed, AWS itself has started improving too.
      - mibollma 4y ago
        I've used both and I would still prefer ecs/fargate to build a rather independent application and k8s to build a long-term platform.
- thaneross 4y ago
  A compelling reason is the large ecosystem of tooling that runs on k8s. Practically anything you want to do has a well maintained open source project ready to go.
  - tuxie_ 4y ago

hobofan 4y ago

+1. GKE Autopilot and sticking to the core ~4 Kubernetes object kinds (Deplyoment, Service, Ingress), was a really easy way for us to get started with K8s (and in many cases can carry you a really long way).

amtamt 4y ago
Though easy to run, if there are multiple workloads of varying resource requirements, there will be a lots of wasted CPU and RAM, just because there are minimum CPU and CPU to RAM requirements.
crucialfelix 4y ago
Agree. I think they are working towards providing ISTIO (gateway replaces ingress, TLS internal communication, canary deployments, shadowing etc). If they can spin up GPU or high memory nodes on demand with Autopilot that would be amazing.

evoxmusic 4y ago

There is also a new generation of platform that runs on top of Kubernetes that are emerging. Like Qovery

tuxie_ 4y ago

Why would you run it in k8s as opposed to, say, ECS? Honest question here, why not run it on something simpler that requires less new concepts and achieves the same results?

akvadrako 4y ago
Because ECS sucks. It's slow and unergonomic, like a badly designed k8s with fewer features. k8s is nicer to use and simpler if you ignore the complex bits. Plus it's the standard.
- kungfufrog 4y ago
  My experience of ECS is the opposite of yours. It integrates nicely with the AWS ecosystem and was substantially easier to use and educate others on. Would not hesitate to use again on either fargate or BYO EC2. I will acknowledge scheduling is not quite as fast as Nomad but I never found it 'slow'
  - ownagefool 4y ago
    Personally, I'd rather create a k8s deployment than an ECS task, but I can see your point. If all you want is an integrated with AWS experience, then it makes som sense that ECS is just simpler overall out of the box. I don't think the delta to make k8s integrated is that much work with EKS, but ability to mutate the entire infrastructe if and when you do scale wins out for me. I think the complexity, most of which you can ignore, is worth the flexibility. Either way, since k8s landed, AWS itself has started improving too.
    - mibollma 4y ago
      I've used both and I would still prefer ecs/fargate to build a rather independent application and k8s to build a long-term platform.
thaneross 4y ago
A compelling reason is the large ecosystem of tooling that runs on k8s. Practically anything you want to do has a well maintained open source project ready to go.
- tuxie_ 4y ago