You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Filling this so it gets tracked, although an upstream release (of grpc-go) is not ready yet that I know of.
Summary
Due to a bug in grpc-go, go grpc clients that communicate over a unix domain socket currently can not communicate with strict server implementations due to an empty authority header.
This should only affect nomad through CSI plugin support, as iirc no other grpc communication goes through a UDS.
I'm going to lock this issue because it has been closed for 120 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.
Filling this so it gets tracked, although an upstream release (of grpc-go) is not ready yet that I know of.
Summary
Due to a bug in grpc-go, go grpc clients that communicate over a unix domain socket currently can not communicate with strict server implementations due to an empty authority header.
This should only affect nomad through CSI plugin support, as iirc no other grpc communication goes through a UDS.
See the following issue (and linked GRPC issues): kubernetes/kubernetes#93320
The text was updated successfully, but these errors were encountered: