Use best practices to run external CCM

[dims]

From @dims on March 21, 2018 18:57

This list is from @andrewsykim

• use hostnetwork: true so you don't depend on CNI to initialize nodes
• use dnsPolicy: Default since kube-dns likely doesn't tolerate the node.cloudprovider.kubernetes.io/uninitialized taint
• tolerate node-role.kubernetes.io/master since you probably want it running on master nodes
• use --leader-elect if you want HA

Copied from original issue: dims/openstack-cloud-controller-manager#92

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[fejta-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten
/remove-lifecycle stale

[fejta-bot]

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close