Browse Source
Fix proxy usage when *_PROXY are present in environment (#7309)
Fix proxy usage when *_PROXY are present in environment (#7309)
Sincepull/7368/heada790935d02
all proxy users should be properly configured Now when you have *_PROXY vars in your environment it can leads to failure if NO_PROXY is not correct, or to persistent configuration changes as seen with kubeadm in1c5391dda7
Instead of playing constant whack-a-bug, inject empty *_PROXY vars everywhere at the play level, and override at the task level when needed Signed-off-by: Etienne Champetier <e.champetier@ateme.com> (cherry picked from commit067db686f6
)
Etienne Champetier
3 years ago
committed by
Kubernetes Prow Robot
14 changed files with 51 additions and 13 deletions
Split View
Diff Options
-
13cluster.yml
-
4recover-control-plane.yml
-
4remove-node.yml
-
2reset.yml
-
1roles/download/tasks/prep_kubeadm_images.yml
-
1roles/kubernetes/kubeadm/tasks/kubeadm_etcd_node.yml
-
5roles/kubernetes/kubeadm/tasks/main.yml
-
1roles/kubernetes/master/tasks/kubeadm-fix-apiserver.yml
-
4roles/kubernetes/master/tasks/kubeadm-secondary.yml
-
5roles/kubernetes/master/tasks/kubeadm-setup.yml
-
1roles/kubernetes/master/tasks/kubeadm-version.yml
-
1roles/kubernetes/node/tasks/kubelet.yml
-
8scale.yml
-
14upgrade-cluster.yml
Write
Preview
Loading…
Cancel
Save