-
-
Notifications
You must be signed in to change notification settings - Fork 291
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Why is the schema of the api server url fixed to HTTPS,can it support configurable features? #1476
Comments
I found an environment variable: KUBE_RS_DEBUG_OVERRIDE_URL that can solve the problem https://github.com/kube-rs/kube/blob/main/kube-client/src/config/mod.rs#L339 |
huh, thanks for the post. i am not sure whether or not this is a bug or not. in particular i would have expected the else branch in that fn to return http on non-443 ports, but maybe non-https apiserver access is generally not something that is available? Are you doing some type of local development? (The |
Pretty sure the apiserver intentionally dropped plaintext HTTP support a while ago. This is also only relevant to incluster, Kubeconfig does support plaintext HTTP. That said, it seems completely pointless to keep singling out all those |
ok, thanks, in my case, the k8s api server only support http, i will try to use it (Config) |
Can't agree any more, https will become a strict standards. |
All that said, please don't use plaintext K8s outside of local testing. Exposing plaintext K8s is like exposing unencrypted telnet. It's remote code execution with no ifs or buts around it. |
kube/kube-client/src/config/incluster_config.rs
Line 64 in 79d23a0
The text was updated successfully, but these errors were encountered: