[andrewstuart2]

Man, this is definitely useful, but I hope you'd agree with me when I say that I hope you can safely get rid of this tool in the near future. I really want to see a better way of reusing resources in k8s (for example, a first-class Environment object that mimics /etc/environment).

I'd really like to get rid of my custom hacky kubectl wrapper scripts and either just use a cluster add-in or have a kubectl build-in processor that helps reuse.

[hosh]

If you know Ruby and how class inheritance work and don't mind reading source code, check out my https://github.com/matsuri-rb/matsuri

I wrote that one after putting into production: bash scripts (for Docker), Docker Compose, AWS ECS, and finally K8S. It was designed to reuse Kubernetes resources, but doing it in a way where it takes into account differences across environments.

Some of the code is old though. There is a whole part that brings up K8S in a container, which with microkube, nanokube, and kubeadm should just be taken out completely of Matsuri. It would also be great if I get an example repo written as a starter kit for people.

That said: have you checked out Helm? Helm overlaps Matsuri in functionality, is better documented and doesn't require you to know Ruby.