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

Container method can avoid ifconfig magic and socat... #726

Closed
ark3 opened this issue Aug 6, 2018 · 2 comments
Closed

Container method can avoid ifconfig magic and socat... #726

ark3 opened this issue Aug 6, 2018 · 2 comments

Comments

@ark3
Copy link
Contributor

@ark3 ark3 commented Aug 6, 2018

... by using ssh port forwarding. Instead of connecting from the local container to the host machine (and then using socat to get from the Docker interface to the kubectl port forward interface), we can connect from the host machine into the local container and then ssh port forward from the container's localhost to the kubectl port forward. This would avoid fussing with Docker interfaces and host.docker.internal and so forth, in exchange for having to run an ssh daemon in the network container.

@ark3 ark3 added the t:feature label Aug 6, 2018
@ark3 ark3 added this to To do in Tel Tracker via automation Aug 6, 2018
@ark3
Copy link
Contributor Author

@ark3 ark3 commented Aug 10, 2018

Doing this would entirely sidestep #224, #467, and #647, along with possibly other container method issues.

@ark3
Copy link
Contributor Author

@ark3 ark3 commented Aug 14, 2018

And #735

@ark3 ark3 closed this in #855 Dec 5, 2018
Tel Tracker automation moved this from To do to Done Dec 5, 2018
ark3 added a commit that referenced this issue Dec 5, 2018
Reach cluster from local container via ssh tunnel instead of ifconfig/socat
Fixes #726
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
1 participant