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

Fixed Issue #13 gateway has no own kubectl, also from context of section we are talking about local machine, and next command "kubectl get nodes" could be only on local machine run #16

Closed
wants to merge 1 commit into from

Conversation

mogol07
Copy link

@mogol07 mogol07 commented Sep 5, 2024

Fixed #13

…t of section we are talking about local machine, and next command "kubectl get nodes" could be only on local machine run
@mogol07 mogol07 marked this pull request as ready for review September 5, 2024 17:39
@jceb
Copy link
Member

jceb commented Feb 10, 2025

Yes, you're right, the execution on the local machine should be emphasized. I don't want to add the -fN flags, because this makes it difficult to shut down the connection. I will instead improve the docs.

@jceb jceb closed this Feb 10, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

port forarding doesn't correct described in readme
2 participants