Re:How Docker broke in half
by bashinator on Wednesday September 08, 2021 @08:14PM
(#28464642)
Coming from a long career in ops and systems administration, k8s was very straightforward to learn. All the complexity is in automating the things that I’ve already had to know how to do - scaling, failover, resource planning, etc etc.
Re:How Docker broke in half
by fiddlerwoaroof on Thursday September 09, 2021 @01:43AM
(#28466664)
Yeah, this stuff is complicated any way you go: puppet, chef, ansible, Cloudformation/CDK, Terraform, K8s all have non-zero learning curves.
You're trading for structured environment at the cost of complexity for sure, but I think there's something to be said about the degree of complexity. Ansible for example only requires python + some handful library + ssh connection whereas Chef/Puppet requires agent install + SSL for correct functionality.
- deploying k8s on bare metal is not easy. It was never really designed for this and to be fair Google has a vested interest in making you use GCP. EKS is nothing more than cobbled together scripts and you still need to do a lot of manual work
- k8s introduces a ton of terminology and new concepts (pods/service/deployment/ingress) not to mention the whole host of addons built on top like Istio.
It shouldn't take any decent dev more than a couple days to install minikube/k3s or use a cloud provider, play around and get comfortable with k8s.