HTTP proxy support for cloud provider interactions

[MatthiasWinzeler]

As discussed in #126

[cfdreddbot]

Hey MatthiasWinzeler!

Thanks for submitting this pull request! I'm here to inform the recipients of the pull request that you and the commit authors have already signed the CLA.

[cf-gitbot]

We have created an issue in Pivotal Tracker to manage this:

https://www.pivotaltracker.com/story/show/153135793

The labels on this github issue will be updated when the story is started.

[glestaris]

hey @MatthiasWinzeler, sorry for dropping the ball on this.

Why is the kubelet-password property exposed?

[glestaris]

also, can we extend this to https_proxy for consistency with https://github.com/cloudfoundry-incubator/docker-boshrelease/blob/889931ecf134493ab4471fb3b9e482be3b628628/jobs/docker/spec#L127?

[MatthiasWinzeler]

@glestaris looks like kubelet-password came with this merge afterwards: 45f41af
It's not related to the PR and probably can be removed...

I think it's fine to also expose https_proxy. For us, it was not needed, since http_proxy also applies to https urls (golang's default behavior).

[glestaris]

👍 thanks, we will look into merging this soon

[ryanjjones10]

As an update, this is top of backlog for CFCR and is expected to be in the next release, 0.14. This is not expected to be in PKS 1.0 but will be added shortly after to one of the alphas if you all are interested in taking those in.

[glestaris]

@MatthiasWinzeler the commits are merged. I am closing the PR.

[MatthiasWinzeler]

@glestaris great news, thank you!

[akshaymankar]

Thanks for your help with the no_proxy thing @MatthiasWinzeler