-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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
csi plugins receiving invalid/incorrect authority header #5346
Comments
I'm confused, is this a K3s specific issue, or did you report it here because that's where you reproduced it? This seems like something that should be tracked in the grpc-go, kubernetes, or democratic-csi projects. Is there anything you believe we could do to resolve this problem within K3s? |
@brandond the problem was supposedly resolved in |
Yeah, HTTP over Unix sockets is weird for sure. With the |
From what I've seen the common consensus seems to be setting the value to |
Environmental Info:
K3s Version: present in all known versions
Node(s) CPU architecture, OS, and Version: NA
Cluster Configuration: NA
Describe the bug:
grpc-go
in certain circumstances sends the path to the uds as the host/authority header. This is seemingly non-compliant and many http2 servers outright reject the request.I've created a project here to circumvent the issue: https://github.com/democratic-csi/csi-grpc-proxy
Further discussion here: democratic-csi/democratic-csi#164
Steps To Reproduce:
Expected behavior:
Driver comes up healthy and is properly registered with kubelet etc.
Actual behavior:
kubelet
fails to register the driver. Error looks something like this:Additional context / logs:
Backporting
The text was updated successfully, but these errors were encountered: