ProxyError('Cannot connect to proxy.', error('Tunnel connection failed: 407 authentication required',))

[erlisb]

What happened (please include outputs or screenshots):
I am trying to use proxy in the kubernetes framework but I get the following error :

 urllib3.exceptions.MaxRetryError: HTTPSConnectionPool(host='lcageanaksd-1dffcee1.hcp.westeurope.azmk8s.io', port=443): Max retries exceeded with url: /api/v1/nodes (Caused by ProxyError('Cannot connect to proxy.', error('Tunnel connection failed: 407 authentication
required',)))

What you expected to happen:
Here I suppose I would get the list of nodes.

How to reproduce it (as minimally and precisely as possible):

    self.client_config = Configuration()
    self.client_config.debug = False
    self.client_config.verify_ssl = ssl
    self.client_config.assert_hostname = False
    self.client_config.host = url
    self.client_config.proxy = proxy_url
    self.client_config.debug = True
    self.client_config.api_key.update({'Authorization': 'Bearer {}'.format(TOKEN)})
    ApiClient = client.ApiClient(self.client_config)
    v1 = client.CoreV1Api(ApiClient)
   v1.list_node()

Anything else we need to know?:

Environment:
Kubernetes Client Version: v1.11.0+d4cacc0
AKS Kubernetes Server Version: v1.12.7
Python 2.7.15rc1

[roycaihw]

You need to pass in proxy headers to properly use the proxy manager. Ref #779, OpenAPITools/openapi-generator#2467

This should be fixed in the upcoming 12.0.0a1 release where we upgrade to a newer version of openapi-generator. You can apply the fix locally as a workaround

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[fejta-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten

[fejta-bot]

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

[k8s-ci-robot]

@fejta-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/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/test-infra repository.