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

Accessing the Private Cluster HTTPS_PROXY value #17

@yujikiriki

Description

@yujikiriki

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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions