Skip to content
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

Ability to "tunnel" from localhost to service group or port forward to an instance #1495

Closed
nderjung opened this issue Apr 3, 2024 · 1 comment · Fixed by #1680
Closed
Assignees
Labels
kind/enhancement New feature or request priority/low Nice to have issues thatare not urgent, but can be nagging.

Comments

@nderjung
Copy link
Member

nderjung commented Apr 3, 2024

Feature request summary

This issue tracks the ability to let the user access the internal network and/or internally exposed ports of application services within a KraftCloud service group.

The purpose of this is to let users a). connect to services which are typically not exposing TLS-based traffic, which KraftCloud only supports and b). debug instances without having to publicly expose the port.

This should manifest itself as a new CLI subcommand:

kraft cloud tunnel <SERVICE|INSTANCE> [PORT[:PORT[/PROTOCOL]

Where then:

  • kraft cloud tunnel my-service -- forwards everything, you can do ping on instances in the same service group. Needs some thinking and sounds more complex to do.
  • kraft cloud tunnel my-instance 8080 -- forwards port 8080 on localhost to 8080 of the instance my-instance.
  • kraft cloud tunnel my-instance 1234:8080 -- accessing localhost:1234 allows accessing 8080 of my-instance.
  • kraft cloud tunnel my-instance 1234:8080/udp, same as above, only for UDP.
@nderjung nderjung added the kind/enhancement New feature or request label Apr 3, 2024
@craciunoiuc
Copy link
Member

to investigate https://github.com/sumup-oss/gocat

@craciunoiuc craciunoiuc added the priority/low Nice to have issues thatare not urgent, but can be nagging. label Apr 3, 2024
@craciunoiuc craciunoiuc assigned antoineco and unassigned craciunoiuc Apr 5, 2024
antoineco added a commit that referenced this issue Apr 8, 2024
GitHub-Issue: #1495

Signed-off-by: Antoine Cotten <antoine@unikraft.io>
antoineco added a commit that referenced this issue Apr 8, 2024
GitHub-Issue: #1495

Signed-off-by: Antoine Cotten <antoine@unikraft.io>
antoineco added a commit that referenced this issue Apr 8, 2024
GitHub-Issue: #1495

Signed-off-by: Antoine Cotten <antoine@unikraft.io>
antoineco added a commit that referenced this issue Apr 8, 2024
GitHub-Issue: #1495

Signed-off-by: Antoine Cotten <antoine@unikraft.io>
antoineco added a commit that referenced this issue Apr 8, 2024
GitHub-Issue: #1495

Signed-off-by: Antoine Cotten <antoine@unikraft.io>
antoineco added a commit that referenced this issue Apr 8, 2024
GitHub-Issue: #1495

Signed-off-by: Antoine Cotten <antoine@unikraft.io>
@antoineco antoineco removed their assignment Apr 11, 2024
@craciunoiuc craciunoiuc self-assigned this May 31, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/enhancement New feature or request priority/low Nice to have issues thatare not urgent, but can be nagging.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants