3 ms·

everybody who doesn't writes thousands of shell scripts/ansible/puppet whatever stuff to emulate a small version of kubernetes

• raffraffraff 6y ago
  Which is exactly what I did in my previous job before Kubernetes existed. When you're cobbling things together yourself you can leave features out of the design of your deployment / orchestration system. That is a blessing and a curse. A lot of the time you just end up ducktaping that feature on later because "oh shit, it keeps breaking". Eventually your "simpler" system is just as complex a design, but the system has lots of major flaws: * It doesn't work as well * Nobody outside your company has heard of it * Most of the code is once-off hacky scripts that nobody really maintains * Breakages will occur when underlying dependencies get upgraded when you patch your OS. I'll even wager that nobody inside your company completely understand how it works. And when it breaks, you are 100% on the hook for it. There's no chance of official documentation or training, and no point asking for help on stackoverflow.
  • merb 6y ago
    well I did this as well that's why I'm pro k8s. heck setting up k8s and then deploying with that is certainly 1000 times easier than my ansible script was. worse my ansible script had a small downtime. k3s does not have that. the problem is a lot of people try to solve a problem with k8s that k8s does not solve. k8s is mostly a deployment scheduler with application configuration and an api for secrets. thats it. it comes with an api for loadbalancer and ingress but it does not have one built in, but you can schedule these things with it. so basically even your low level primitives can be scheduled with the same api.