Skip to content
This repository has been archived by the owner on Jan 2, 2023. It is now read-only.

Accessing the Private Cluster HTTPS_PROXY value #17

Open
yujikiriki opened this issue Jun 29, 2020 · 0 comments
Open

Accessing the Private Cluster HTTPS_PROXY value #17

yujikiriki opened this issue Jun 29, 2020 · 0 comments

Comments

@yujikiriki
Copy link

yujikiriki commented Jun 29, 2020

Following the guide, I found that this was not working in my setup (Linux x86-64, running bash):

alias k="HTTPS_PROXY=localhost:8888 kubectl"

I changed to

alias k="HTTPS_PROXY=http://localhost:8888 kubectl"

because of the following error message when running any command with kubectl:

Unable to connect to the server: proxyconnect tcp: tls: first record does not look like a TLS handshake

I replicated the issue with curl -v -I --proxy https://localhost:8888 google.com:

curl: (35) error:1408F10B:SSL routines:ssl3_get_record:wrong version number

Is highly possible that I'm missing something.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant