We have a growing list of components that deploy to Toolforge kubernetes using this pattern:
[x] git repository with source code
[x] checkout on a docker builder host
[x] build the docker image, tag it, etc
[x] upload to our internal docker registry
[] checkout git repository on k8s control node
[] kubectl apply a manifest
[] [optionally] manage auth things, like certificates etc
This is a very good candidate for automation using spicerack/cookbook or whatever.
Known cases:
* 3 custom admission controllers: https://wikitech.wikimedia.org/wiki/Portal:Toolforge/Admin/Kubernetes/Deploying#custom_admission_controllers
* maintain-kubeusers
* jobs-framework-api
* jobs-framework-emailer
NOTE: there is now a spicerack cookbook to automate some of this: `cookbook wmcs.toolforge.k8s.component.build`