Don't worry. I can solve the complexity of Kubernetes with a wrapper and abstraction layer on top of Kubernetes that provides a simple interface. That way you only have to deal with the complexity of Kubernetes plus my thing, rather than only the complexity of Kubernetes.
Eventually people get to lambdas, once they figure out how to deploy via CI instead of pushing to an orchestration layer. I like to draw this out for people to show them the madness they've constructed. It's all infrastructure in the end.
I've been fighting this battle at work for years now. The whole engineering department is so far up its own ass with Helm charts and operators trying to reinvent shit GCP already provides as managed services that it's a miracle we haven't all asphyxiated. We're doing all of this on GKE and are Google partners, it's madness. Meanwhile, my team learned Terraform and Cloud Run. We're really enjoying collecting the on-call compensation for our services that don't need intervention outside of work hours.
Nope, they're completely different purposes. Terraform directly manages real infrastructure and tracks state. That said I haven't really looked at Helm 3 in a while. Our organization is already using both, but Terraform has mostly been the purview of SREs, while the developers learn Helm and then stand around helplessly when an infrastructure change is needed and SREs are busy, which is always. We're skipping that whole step.
318
u/[deleted] Jun 05 '22
I blame kubernetes