Wikimedia Release Engineering Team/Deployment pipeline/2018-04-26

Last Time

 * 2018-04-12

General

 * Local dev of interest looks neat: https://github.com/GoogleContainerTools/skaffold#demo
 * uses https://github.com/fsnotify/fsnotify to rebuild image and redeploy to minikube locally as part of development

RelEng

 * Checkout this sweet pipeline guys:
 * jjb changes + new CI agents + mathoid helm chart = working pipeline
 * https://integration.wikimedia.org/ci/blue/organizations/jenkins/service-pipeline-test-only-debug/detail/service-pipeline-test-only-debug/24/pipeline (build of https://gerrit.wikimedia.org/r/#/c/425914/ )
 * minikube working - hopefully k8s for CI next
 * What is the timeline?
 * There is a budget, but no real timeline
 * releng and ops need to work it into their plans
 * distinction between a k8s cluster as a target for deploys and a k8s cluster for running CI tests
 * The staging cluster is the target for k8s deployments
 * The k8s cluster for running CI tests is the thing we need to plan around
 * RelEng: to create document for the CI test use-case of k8s
 * SRE: to talk about replacing the e2e minikube use with either the k8s staging cluster or some other yet undecided cluster
 * Next services to migrate
 * blubber supports python now
 * otto seemed excited about moving some python services
 * graphoid (citoid possibly next)

SREs
Preliminary docs in https://wikitech.wikimedia.org/wiki/Kubernetes/Helm

Services
Hackathon idea: local development environment with k8s minikube

= As Always =
 * Release Pipeline Workboard
 * Meeting notes