Websocket tunnel #27
Merged
Websocket tunnel #27
Conversation
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
siliconbrain
force-pushed
the
websocket-tunnel
branch
4 times, most recently
from
2626a2e
to
48f1a75
Compare
And also overhaul the codebase because it was too oldschool
siliconbrain
force-pushed
the
websocket-tunnel
branch
from
48f1a75
to
aefbe75
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What's in this PR?
Replace inlets and ghostunnel with our own tunnel implementation that can terminate TLS and uses the API server proxy instead of a port forward.
The changes also include some refactoring and dropping legacy code.
This PR:
port-forwardcommand can be overridden using the--server-imageflagkurun-server)Why?
Inlets is no longer available as a free-to-use tool.
To Do