Kubernetes has fairly quick release cycles - they're trying to put out a major release every 2-3 months, and minor bugfix releses are far more frequent. We need to figure out our policy for upgrading. They provide fairly strong API guarantees, so upgrading quick and often should be the most painless process.

Based on ideas from @chasemp about how Phab updates are done, I suggest:

1. We have a set 2h window every two weeks.
2. In this window, we upgrade to the latest version of k8s that we expect to work for us. This includes both minor point releases and major releases that don't break api compat. Since APIs are versioned independently of k8s versions, this should be mostly fine.
3. We don't *have* to use the window.

We'd also have differnet people do the deploys, so that we'll have it super automated, documented and simplified :)

Thoughts?