Come up with a better way to handle interrupted connections

[helgi]

Most of the time Deployments continue when HTTP connection is severed between our CLI and our API. However, if bad config/image etc is pushed then we are not in as nice of a spot. Things like DB records and so on are not cleaned up and you end up in with an "In Progress" Deployment (see below for one possible solution)

Deployments have a few things on the Kubernetes roadmap (https://github.com/kubernetes/community/wiki/Roadmap:-Deployment) but there is nothing we can depend on in the near term

See #1071 for more context

[Cryptophobia]

This issue was moved to teamhephy/controller#52