Revert proxies to the old methodology using kubespray-defaults

[billykwooten]

What type of PR is this?

/kind bug

What this PR does / why we need it:

The new method of proxies using cluster.yml, and removing proxies from kubespray-default role causes issues on hosts resulting in get_url throwing the following:

2020-05-08 07:28:27,441 p=9123 u=root n=ansible | TASK [download : download_file | Download item] ********************************
2020-05-08 07:28:27,443 p=9123 u=root n=ansible | fatal: [ldk00474.homedepot.com -> 10.16.34.255]: FAILED! => {"attempts": 4, "changed": false, "dest": "/tmp/releases/kubeadm-v1.17.5-amd64", "elapsed": 10, "msg": "Request failed: <urlopen error [Errno 99] Cannot assign requested address>", "url": "https://storage.googleapis.com/kubernetes-release/release/v1.17.5/bin/linux/amd64/kubeadm"}
2020-05-08 07:28:27,531 p=9123 u=root n=ansible | fatal: [ldk00473.homedepot.com -> 10.16.36.139]: FAILED! => {"attempts": 4, "changed": false, "dest": "/tmp/releases/kubeadm-v1.17.5-amd64", "elapsed": 10, "msg": "Request failed: <urlopen error [Errno 99] Cannot assign requested address>", "url": "https://storage.googleapis.com/kubernetes-release/release/v1.17.5/bin/linux/amd64/kubeadm"}

Which issue(s) this PR fixes:

Fixes #6108

Does this PR introduce a user-facing change?:

 - Reverted to the old proxy methodology due to playbook issues

[k8s-ci-robot]

Hi @billykwooten. Thanks for your PR.

I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: billykwooten
To complete the pull request process, please assign luckysb
You can assign the PR to them by writing /assign @luckysb in a comment when ready.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[billykwooten]

Please see #6112