Deployment rollout monitoring revamp

[KnVerey]

The fact that deployment rollout monitoring currently looks at all pods associated with that deployment instead of pods in the new ReplicaSet has caused several different bugs:

• Deploys never succeed when there are evicted pods associated with the deployment, even though those pods are old (fixed another way)
• Pod warnings get shown for pods that are being shut down, in the case where the last deploy was bad and the current one is actually succeeding (very confusing output)
• Deploy success is delayed by waiting for all old pods to fully disappear
• This false-positive deploy result is likely caused by this. Last poll before it "succeeded" was: (I now think it probably briefly became available before failing a probe, or something like that)

[KUBESTATUS] {"group":"Deployments","name":"jobs","status_string":"Waiting for rollout to finish: 0 of 1 updated replicas are available...","exists":true,"succeeded":true,"failed":false,"timed_out":false,"replicas":{"updatedReplicas":1,"replicas":1,"availableReplicas":1},"num_pods":1}

Related technical notes:

• We are selecting related pods using an assumption that they are labelled with the deployment name. I believe this is a bad assumption that has flown under the radar so far because all our templates are labelled this way by convention. The new ReplicaSet version should not do this.
• Here's how kubectl gets old/new rs

[KnVerey]

• We should base the timeout on progressDeadlineSeconds when present.
• With k8s 1.6, we should select pod based on the new ownerRef field.