WIP: v0.7.3 development branch

[jdef]

multiverse packaging changes: https://github.com/mesosphere/multiverse/pull/78

cherry-picks from upstream:

• MESOS: swappable storage backends for frameworkID #759
  • https://github.com/kubernetes/kubernetes/pull/20387
• MESOS: fix nil panic in scheduler procurement #768
  • https://github.com/kubernetes/kubernetes/pull/20936
• MESOS: host port endpoints refactor #785
  • https://github.com/kubernetes/kubernetes/pull/21276
• MESOS: update to latest mesos-go for master failover improvements #582
  • https://github.com/kubernetes/kubernetes/pull/21198
• MESOS: derive driver's published address from LIBPROCESS_IP #790
  • https://github.com/kubernetes/kubernetes/pull/21612
• MESOS: fix k8sm-787 scheduler failover regression #787
  • https://github.com/kubernetes/kubernetes/pull/21768
• MESOS: stop creating sub-containers for kubelet and kube-proxy #762
  • https://github.com/kubernetes/kubernetes/pull/21652
• MESOS: fix argv[0] of executor args; move conntrack args to minion block #594
  • https://github.com/kubernetes/kubernetes/pull/21852

[ravilr]

@jdef i believe all the changes here are going to be part of the upstream k8s-1.2 release. Will i be missing anything when building k8sm using upstream repo? Thanks.

[jdef]

@ravilr we've tried to follow a process of merging to master, then cherry-picking/backporting to our stable release fork.

the UI in this fork is different than what's in 1.2, but 1.2 is shipping with kube-dashboard now anyway

there's also a bandaid PR in this fork for an issue that hasn't been properly addressed here, but HAS been addressed in 1.2 and master (https://github.com/kubernetes/kubernetes/pull/18966/files?w=1)

the upstream/release-1.2 branch should not be missing anything