4 ms·
The entire contemporary devops process is awfully convoluted. In fact, I've heard DevOps people call themselves "yaml engineers". Often in your docker compose t
by spectramax 7y ago
The entire contemporary devops process is awfully convoluted. In fact, I've heard DevOps people call themselves "yaml engineers". Often in your docker compose there is some stupid error, there are 3 versions of Docker compose files, there are 7 ways to do something, Docker CLI manual can be printed in 1000 pages and we've created extremely bloated (despite of caching whatever) CI/CD. For what? Dependencies? Let's download 4.5 GB of images because my app needs to be reproduceable.
I tried reading about Kubernetes. Holyshit what a monster we've created. I am sure there is going to be an orchestrator abstraction for multiple Kubernetes clusters. And then we have environment variables, secrets, access keys, a bazillion different parameters that need to trickle down from Gitlab CI settings all the way to the app through many layers.
Good lord. All engineers should be ashamed of this mess. We've forgotten how to build simple, beautiful, lean and parsimonious software. Instead of writing logic, I am configurating things all day.
Let there be a day where there is some deep compiler problem and this entire house of cards comes crashing down because your DevOps team ain't gonna know what happened down in lower abstraction layers. But, let's shit on the F-35 program everytime there is a Lockheed article on HN. Because surely, software engineers are the smart bunch ya. I know, I am unreasonably obtuse here, but jeez, no one complains about today's deployment process,... its apparently accepted without a question.
- rraghur 7y ago> Let there be a day where there is some deep compiler problem and this entire house of cards comes crashing down because your DevOps team ain't gonna know what happened down in lower abstraction layers I'm with you on the feeling that modern stack is bloated and heavy... However, this is exactly the scenario where the compiler bug is isolated quickly because you're not chasing dependency differences between boxes
- spectramax 7y agoNo! What if there is a bug in Kubernetes itself? or in the Docker engine? Or a compiler bug that affects Kubernetes in mysterious ways?
- empath75 7y agoWhat if there is a bug in kubernetes or docker? There are tons of them, people find new ones all the time. You troubleshoot it like every other problem. Hell, you’ve barely scratched the surface of all the ways a kubernetes install can break — coredns? Etcd? Nginx? Istio? My god what if there’s a bug in the Linux kernel? We should just give up, computers were a mistake.
- aliswe 7y agoWith all due respect this argument in itself simply is not valid. The engine itself runs, but you WILL need a driver.
- ryall 7y agoMulti-zone reproducible HA environments are complex. Who'da thunk it?
- aliswe 7y agoKubernetes and Docker is about moving complexity, not removing complexity. I recently held a presentation for our UK applications team (manager, team lead) about our setup from a provisioning perspective, release process perspective, organizational perspective, QA perspective, operations perspective, troubleshooting perspective, full traceability, ease-of-deployment, time-to-market. Needless to say they were amazed to see that we can deploy a new isolated, "virtual machine" application running in seconds using dynamic DNS, rather than waiting a year for a new application server from the IT organization not to speak about deploying it, operating it and troubleshooting it.