I'm a sysadmin and I attended KubeCon recently. I came back with a similar thought flow in mind. This one anecdote nailed the problem in my opinion - "Kubernetes makes simple things hard, and hard things possible." So, if you dont have things that you think are impossible, just don't pay the complexity tax.
Paraphrasing for discussion:
Poster: A rails project with deployed to 6 servers running in production currently.
Poster: During the asset compilation process, the servers often freeze.
Poster: I need to manually remove servers from the load balancer and deploy one by one.
Poster:I looked a lot into kubernetes and production containerization lately, and as far as I read it, it should solve the deployment and uptime issues. I imagine it'd be a lot easier to just switch containers instead of deploying with capistrano. I also really like the self-healing capabilities a lot.
So, he/she hopes that Kubernetes will magically solve his problem(asset compilation freezes the server). I suppose in his/her mind, Kubernetes is the snake oil.
Things that he/she failed to put thought into (and rather got revved up about Kubernetes):
* Could I setup CI with a script that will perform the asset compilation once on one server and just rsync the final result to the prod servers?
* Could I spend a couple of hours understanding the asset compilation process and find out why it freezes the server?
* Could I learn more about load balancing, rolling deploys?
I think this is the real problem in the tech field. People are running after shiny tools and hope to through tools at their problems all the while ignoring the basics.
In this particular case, I think if they had a grey beard sysadmin who was grumpy to the devs, and enforced a strict release process, everyone would've been happier.
Real-life example : https://www.reddit.com/r/devops/comments/8byasq/is_kubernete...
Paraphrasing for discussion: Poster: A rails project with deployed to 6 servers running in production currently.
Poster: During the asset compilation process, the servers often freeze.
Poster: I need to manually remove servers from the load balancer and deploy one by one.
Poster:I looked a lot into kubernetes and production containerization lately, and as far as I read it, it should solve the deployment and uptime issues. I imagine it'd be a lot easier to just switch containers instead of deploying with capistrano. I also really like the self-healing capabilities a lot.
So, he/she hopes that Kubernetes will magically solve his problem(asset compilation freezes the server). I suppose in his/her mind, Kubernetes is the snake oil.
Things that he/she failed to put thought into (and rather got revved up about Kubernetes):
* Could I setup CI with a script that will perform the asset compilation once on one server and just rsync the final result to the prod servers?
* Could I spend a couple of hours understanding the asset compilation process and find out why it freezes the server?
* Could I learn more about load balancing, rolling deploys?
I think this is the real problem in the tech field. People are running after shiny tools and hope to through tools at their problems all the while ignoring the basics.
In this particular case, I think if they had a grey beard sysadmin who was grumpy to the devs, and enforced a strict release process, everyone would've been happier.