Due to suboptimal external loadbalancer configs, the LoadBalancer
might point to a downed kube-apiserver that is not set up yet.

* Update DNS Autoscaler to latest

* Update CoreDNS to latest

* Update KubeDNS to latest

* Add KubeDNS config map

* Fix filename

* Add missing selector to DNS Autoscaler

* Add missing tolerations

* Enable AutoScaler for CoreDNS

* Only use one template for dns autoscaler

* Rename a few variables for replicas and minimum pods

* Rename a few variables for replicas and minimum pods

* Remove replicas to make autoscale work

* Cleanup kubedns-autoscaler as it has been renamed

* weave: Upgrade to 2.5.0

Upstream Changes:

-   weave 2.5.0 (https://github.com/weaveworks/weave/releases/tag/v2.5.0)
-   Adds support for Kubernetes `hostPort` mapping
-   Adds support for Kubernetes `ipBlock` NetworkPolicy feature

Our Changes:

-   Templates sync with upstream manifests
-   Remove legacy nodePort fix

* BC for weave < 2.5.0

add prometheus annotations to calico-node if
calico_felix_prometheusmetricsenabled is enabled.

This will allow a kubernetes_sd to automaticly find the pods and start
scraping.

* Revert netchecker image and version

* Create namespace for netchecker

* Remove extra slashes

Fix gen_tags.sh script

Set kubernetes node labels from a given comma-separated list of `key=value` from AWS instance tag `kubespray-node-labels`.

Use case is when kubespray runs from unprivileged user without sudo permission.

* Apply linux node selector to coreDNS deployment

* Remove comment before linux node selector on manifests

* mend

the ':' makes wrong return of calico_version after the calicoctl downloaded && before the cluster is up

* Update ha-mode.md

* Remove Vault

* Remove reference to 'kargo' in the doc

* change check order

Signed-off-by: mooncake <xcoder@tenxcloud.com>

As Ubuntu Bionic Beaver uses systemd-networkd the step fails
if it tries to restart networking, as it is nonexistent.

reset role hang and can't umount PersistenceVolume (ceph cluster)

This is rather convenient if you want to configure exceptions on a
company firewall.

This give users the option to define multiple ssh public keys when
deploying the base infrastructure on Azure.

* Fix Failure talking to yum: Cannot find a valid baseurl for repo: base/7/x86_64 if Install packages in CentOS using proxy

* Add proxy to /etc/yum.conf if http_proxy is defined