Comment 4 for bug 1814968

There are 2 issues found in the log:

1. helm init error.
The docker proxy patch is for docker image pulling, this setting only affects docker daemon.
For helm, it is a new issue that helm init uses system proxy setting which is not set previously.

Moreover, for those who do not have public internet access, https://kubernetes-charts.storage.googleapis.com is not accessible and helm does have a flag for setting stable repo url. see https://github.com/helm/chart-testing/issues/33

2. kubeadm error.
From the log, it seems that you repeatly did the first time controller-1 unlock and the manifests for k8s components are already generated. kubeadm will stop if detect these manifests exists.

2019-02-06T13:52:40.300 Notice: 2019-02-06 13:52:40 +0000 /Stage[main]/Platform::Kubernetes::Master::Init/Exec[configure master node]/returns: [preflight] Some fatal errors occurred:
2019-02-06T13:52:40.301 Notice: 2019-02-06 13:52:40 +0000 /Stage[main]/Platform::Kubernetes::Master::Init/Exec[configure master node]/returns: [ERROR FileAvailable--etc-kubernetes-manifests-kube-apiserver.yaml]: /etc/kubernetes/manifests/kube-apiserver.yaml already exists
2019-02-06T13:52:40.303 Notice: 2019-02-06 13:52:40 +0000 /Stage[main]/Platform::Kubernetes::Master::Init/Exec[configure master node]/returns: [ERROR FileAvailable--etc-kubernetes-manifests-kube-controller-manager.yaml]: /etc/kubernetes/manifests/kube-controller-manager.yaml already exists
2019-02-06T13:52:40.305 Notice: 2019-02-06 13:52:40 +0000 /Stage[main]/Platform::Kubernetes::Master::Init/Exec[configure master node]/returns: [ERROR FileAvailable--etc-kubernetes-manifests-kube-scheduler.yaml]: /etc/kubernetes/manifests/kube-scheduler.yaml already exists