pick proxy from kube_config

[kwibus]

What type of PR is this?

/kind feature

What this PR does / why we need it:

kubeconfig support the option proxy-url .
This is option is ignored by this client. and people have trouble to configer there proxy #1967
This pull request will use that option to set kubernetes.client.load_kube_config()' to set kubernetes.client.configuration.proxy`

Which issue(s) this PR fixes:

Fixes #2183

Special notes for your reviewer:

Does this PR introduce a user-facing change?

`load_kube_config`, ` new_client_from_config_dict`, `new_client_from_config` will use `proxy-url` cluster setting to `set client..configuration.proxy`.

Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.:

[linux-foundation-easycla]

The committers listed above are authorized under a signed CLA.

• ✅ login: kwibus / name: Rens (376f179, f27bb49)

[k8s-ci-robot]

Welcome @kwibus!

It looks like this is your first PR to kubernetes-client/python 🎉. Please refer to our pull request process documentation to help your PR have a smooth ride to approval.

You will be prompted by a bot to use commands during the review process. Do not be afraid to follow the prompts! It is okay to experiment. Here is the bot commands documentation.

You can also check if kubernetes-client/python has its own contribution guidelines.

You may want to refer to our testing guide if you run into trouble with your tests not passing.

If you are having difficulty getting your pull request seen, please follow the recommended escalation practices. Also, for tips and tricks in the contribution process you may want to read the Kubernetes contributor cheat sheet. We want to make sure your contribution gets all the attention it needs!

Thank you, and welcome to Kubernetes. 😃

[roycaihw]

/assign

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all PRs.

This bot triages PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the PR is closed

You can:

• Mark this PR as fresh with /remove-lifecycle stale
• Close this PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[MadJlzz]

@roycaihw any chance we could look at this? I can lend a hand for testing it!

[fabianvf]

This looks good to me

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: fabianvf, kwibus
Once this PR has been reviewed and has the lgtm label, please ask for approval from roycaihw. For more information see the Kubernetes Code Review Process.

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

Needs approval from an approver in each of these files:

• kubernetes/base/OWNERS

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

[fabianvf]

/lgtm

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all PRs.

This bot triages PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the PR is closed

You can:

• Mark this PR as fresh with /remove-lifecycle rotten
• Close this PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the PR is closed

You can:

• Reopen this PR with /reopen
• Mark this PR as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close

[k8s-ci-robot]

@k8s-triage-robot: Closed this PR.

In response to this:

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the PR is closed

You can:

• Reopen this PR with /reopen
• Mark this PR as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close

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-sigs/prow repository.

[MichaelTrip]

Can anybody review this pr again. I need this in a project in which I need to use a proxy url to connect to my Kubernetes api. This is an API endpoint that is not exposed to the public because of security.

[sbahar619]

@MichaelTrip
Hi!
Can this PR reopen again?

[MichaelTrip]

@MichaelTrip
Hi!
Can this PR reopen again?

I am not a contributor nor a maintainer here. I hope somebody reads this and reopens it again.

[sbahar619]

Ohh right, thanks @MichaelTrip
@kwibus
If you can reopen this PR, it will be great, I will try to push it from my side too.

[MichaelTrip]

Ohh right, thanks @MichaelTrip
@kwibus
If you can reopen this PR, it will be great, I will try to push it from my side too.

Kwibus is also not a maintainer nor a contributor here. Maybe you can pull some strings at Redhat to get this PR merged?

[sbahar619]

@kwibus is the one opened this PR...
Sure, I already raised this PR internally.
@MichaelTrip