4 ms·

Why are people still scared of k8s? At certain jobs thresholds, it is worth every ounce of effort to maintain it. Better yet, go managed.

cogman10 3y ago
I honestly don't understand it either. Familiarity? K8s has like, what, 5 big concepts to know and once you are there the other concepts (generally) just build from there. - Containers - Pods - Deployments - Services - Ingresses There are certainly other concepts you can learn, but you aren't often dealing with them (just like you aren't dealing with them when working with something like docker compose).
- nprateem 3y ago
  Good luck fixing etcd when a major version upgrade breaks. It took all weekend to fight that fire when it happened to us.
  - p_l 3y ago
    Been there, done that, didn't get a t-shirt but got to yell at some people for setting up with undersized VMs and forgetting to note it anywhere. Haven't had an issue once I fixed sizing.
  - Thaxll 3y ago
    Use managed k8s, problem solved.
    - nprateem 3y ago
      That problem solved, but plenty of other things hiding in that 'simple' setup of just 5 concepts.
      - cogman10 3y ago
        Which is why you don't lose your SRE/OPS team just because you k8s. I'd say that if you aren't big enough to have dedicated SRE then k8s is not for you. However, it really only takes 1 or 2 people to manage pretty large clusters with 100s or 1000s of deployments. That's where my company currently finds itself.
jakupovic 3y ago
People don't understand k8s and are thus hating. K8s is a wonderful tool for most things many teams need. It may not be useful for homelab type of stuff as the learning curve is steep, but for professional use it cannot be beat currently. Just a bunch of I know what I'm doing and don't need this complicated thing I don't understand. Pretty simple and especially in a forum such as HN where we all are "experts" and need to explain to ourselves, and crucially others, why we are right not to use k8s. Bunch of children really.

cogman10 3y ago

I honestly don't understand it either. Familiarity? K8s has like, what, 5 big concepts to know and once you are there the other concepts (generally) just build from there. - Containers - Pods - Deployments - Services - Ingresses There are certainly other concepts you can learn, but you aren't often dealing with them (just like you aren't dealing with them when working with something like docker compose).

nprateem 3y ago
Good luck fixing etcd when a major version upgrade breaks. It took all weekend to fight that fire when it happened to us.
- p_l 3y ago
  Been there, done that, didn't get a t-shirt but got to yell at some people for setting up with undersized VMs and forgetting to note it anywhere. Haven't had an issue once I fixed sizing.
- Thaxll 3y ago
  Use managed k8s, problem solved.
  - nprateem 3y ago
    That problem solved, but plenty of other things hiding in that 'simple' setup of just 5 concepts.
    - cogman10 3y ago
      Which is why you don't lose your SRE/OPS team just because you k8s. I'd say that if you aren't big enough to have dedicated SRE then k8s is not for you. However, it really only takes 1 or 2 people to manage pretty large clusters with 100s or 1000s of deployments. That's where my company currently finds itself.

jakupovic 3y ago

People don't understand k8s and are thus hating. K8s is a wonderful tool for most things many teams need. It may not be useful for homelab type of stuff as the learning curve is steep, but for professional use it cannot be beat currently. Just a bunch of I know what I'm doing and don't need this complicated thing I don't understand. Pretty simple and especially in a forum such as HN where we all are "experts" and need to explain to ourselves, and crucially others, why we are right not to use k8s. Bunch of children really.