That was an interesting read thanks for sharing it! My takeaway from this is that the k8s codebase is complicated with complicated workflows. Simple tools won't

That was an interesting read thanks for sharing it! My takeaway from this is that the k8s codebase is complicated with complicated workflows. Simple tools won't suffice for this development system. They had to create some of their own tooling; in a way that's quite in line with the usage of k8s, a lot of existing OS concepts had to be recreated just for k8s. > authorization > package management > So why shouldn't a VCS embrace its role as a collaboration tool and explore more generic merge-based optimizations like a queue? In the bottom section there are a few 'wishlist' items, can I call it that. But those aren't good VCS features, they're a reflection of the k8s development world which is not how most of us do development. It's also assuming that because k8s is an all-in-one-doing-many-things, that the VCS it uses should also be a huge all-in-one. I don't think it should; all that would happen is the leaking of k8s' already complex existence from k8s into git. Then it really would break git by making git worse for everyone. I would suggest finding another tool, or making your own.