Allow tunnel to ssh ports#178
Open
lalyos wants to merge 1 commit intoSTRRL:masterfrom
Open
Conversation
Author
|
In case somebody want to test it, I've pushed my image to dockerhub. Where |
This file contains hidden or 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
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.
I wondered if its possible to expose both http and ssh ports of a pod.
In my case I deployed gitea which has both.
After making the tunnel work by manually changing the tunnel configuration, I figgured what was missing:
pathmake sensetcp) type it shouldn't be setWith a simple check I made the controller successfully expose my gitea ssh service via a cloudflare tunnel.
Example
Here is an ingress with all details:
I was using the official helm chart to deploy gitea, and first the svc had a couple of issue:
The final relevant chart values to fix the service:
The content of
values-gitea.yaml