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

port forarding doesn't correct described in readme #13

Open
mogol07 opened this issue Sep 4, 2024 · 1 comment · May be fixed by #16
Open

port forarding doesn't correct described in readme #13

mogol07 opened this issue Sep 4, 2024 · 1 comment · May be fixed by #16

Comments

@mogol07
Copy link

mogol07 commented Sep 4, 2024

Hi!

in readme said

Forward the cluster port locally since it's not exposed to the Internet by default. Do this every time you want to interact with the cluster: ./ssh-node gateway

but this command open new terminal session, not just forwarding port.
To achive only port forwarding, I need to use
./ssh-node gateway -fN

i.e. no run command, only forward port. But to finish process I need to kill process.
Maybe make sense to update readme?

@jceb
Copy link
Member

jceb commented Sep 4, 2024

Hi @mogol07, Thank you for your feedback. Yes, you're right, the command will also open a shell. Would you create a PR to update the documentation accordingly? I'm not sure how useful it is to just get the port forwarded without a shell on the host but feel free to point out this option.

mogol07 added a commit to mogol07/terraform-hcloud-k3s that referenced this issue Sep 5, 2024
…t of section we are talking about local machine, and next command "kubectl get nodes" could be only on local machine run
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
2 participants