Suggestion for a new architecture

[aguerra]

Hi everyone, two cents from a former contributor. Keeping up with the kubernetes API (new features, breaking changes, etc) is unfeasible. We also end up duplicating a lot of kubectl code. One approach for teresa 2.0 might be: give kubectl to the developers and somehow implement access control so each team can only change specific namespaces. Maybe RBAC, maybe an authorization backend, maybe some new k8s feature, etc. This way teresa can be a simple wrapper with sane defaults for kubectl, no more duplication, bumping client-go, etc. About the build process: forget about buildpacks, too complex and have the same problems of bumping, customizing, etc. Each team should be responsible for creating Dockerfiles (we are in 2018!).That's it, good luck!

[yagonobre]

Teresa can be a admission control/controller to enforce all restriction that teresa do today.