Brad Fitzpatrick 71265acedb all: adjust things for upgrade from GKE 1.2 to GKE 1.4 ... We hit GKE bugs and changes when upgrading from GKE 1.2 to 1.4. The main issue is that Kubernetes does't reserve CPU or memory for itself on nodes, so things were OOMing and getting killed. And when Docker or Kubernetes got killed themselves, they were wedging and not recovering. So we're going to run a daemonset (POD on all nodes) to reserve space for Kubernetes for it. That's not in this CL. But this CL got us limping along and was already in production. It doubles resource RAM usage for jobs, so fewer things schedule per node. While we're at it, let jobs use more CPU if it's available. Also, disable auto-scaling. It was off before by hand. Force it off programatically too. And make the node count 5, like it was by hand. Also, force un-graceful pod deletes, since GKE 1.3 or something introduced a graceful-vs-ungraceful distinction, which we weren't handling previously and therefore pods never were being deleted. Change-Id: I3606e4e2e92c496d8194503d510921bd1614d34e Reviewed-on: https://go-review.googlesource.com/33490 Reviewed-by: Brad Fitzpatrick <bradfitz@golang.org>		2016-12-01 23:48:21 +00:00
..
envs.go	all: adjust things for upgrade from GKE 1.2 to GKE 1.4	2016-12-01 23:48:21 +00:00