Add proxy envs to calico to make possible usage of AWS source destination check

[DOboznyi]

After 1.19 update calico was also updated and source-destination check was included in calico natively. So when you're using proxy and cluster created it can't be validated without manual patch:

kubectl set env daemonset/calico-node -n kube-system http_proxy=http://<proxy_url>:<proxy_port>
kubectl set env daemonset/calico-node -n kube-system https_proxy=http://<proxy_url>:<proxy_port>
kubectl set env daemonset/calico-node -n kube-system no_proxy=<no_proxy_list>

Signed-off-by: Dmytro Oboznyi dmytro.oboznyi@syncier.com

[k8s-ci-robot]

Hi @DOboznyi. Thanks for your PR.

I'm waiting for a kubernetes 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.

[hakman]

/ok-to-test

[hakman]

Please also squash the commits. It should be good to merge otherwise.

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: hakman

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

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [hakman]

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