forked from kubernetes-sigs/cri-tools
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
The mentioned issue in 3d04f3b is related to a limitation of cmux, where clients may block until they receive a `SETTINGS` frame. My tests were only related to CRI-O, where an appropriate fix in the project should solve the issue from a general perspective. Nevertheless, a general workaround for end-users trying to connect to a cmux based implementation might be exporting the environment variable `GRPC_GO_REQUIRE_HANDSHAKE=off`. This has been documented in the README.md as well. References: - grpc/grpc-go#2636 - https://github.com/soheilhy/cmux#limitations - cri-o/cri-o#2697 Signed-off-by: Sascha Grunert <[email protected]>
- Loading branch information
1 parent
40d135c
commit 182a6b0
Showing
56 changed files
with
2,072 additions
and
1,194 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Oops, something went wrong.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Oops, something went wrong.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Oops, something went wrong.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Oops, something went wrong.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Oops, something went wrong.
Oops, something went wrong.