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

Support SSH Tunnels #18

Closed
cheftako opened this issue May 31, 2019 · 5 comments
Closed

Support SSH Tunnels #18

cheftako opened this issue May 31, 2019 · 5 comments
Assignees
Labels
lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness.

Comments

@cheftako
Copy link
Contributor

Part of our goals here is to allow SSH Tunnels to be removed from the KAS. If we support SSH Tunnels it would allow a smoother migration plan for users of SSH Tunnels.

@anfernee anfernee self-assigned this Jul 10, 2019
@fejta-bot
Copy link

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Oct 8, 2019
@cheftako
Copy link
Contributor Author

cheftako commented Oct 8, 2019

/remove-lifecycle stale

@k8s-ci-robot k8s-ci-robot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Oct 8, 2019
@cheftako
Copy link
Contributor Author

cheftako commented Oct 8, 2019

/lifecycle frozen

@k8s-ci-robot k8s-ci-robot added the lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. label Oct 8, 2019
@Jefftree
Copy link
Member

@cheftako Quick clarification question: This is supporting SSH tunnels via egress selector correct?

SSH tunnels won't go through the proxy server so this seems to be something on the k/k side and not the network proxy side.

@cheftako
Copy link
Contributor Author

The idea had been to have the proxy/konnectivity server support SSH Tunnels (at least for a little while).
Not a hard requirement, but the thought was it would allow a couple of things.
One could decouple using the konnectivity server from disabling ssh tunnels for clusters using ssh tunnels.
You could first shift to the konnectivity server but retain ssh tunnels.
As a follow on step you could switch to using either http-connect or grpc to the cluster.
This allows you to independently measure the cost of each.
It also allows you have better granularity on any issues which might come up.

alvaroaleman pushed a commit to alvaroaleman/apiserver-network-proxy that referenced this issue Jun 1, 2022
…ncy-openshift-4.11-ose-apiserver-network-proxy

Updating ose-apiserver-network-proxy images to be consistent with ART
River-sh pushed a commit to River-sh/apiserver-network-proxy that referenced this issue Sep 22, 2023
Feature: support custom libreswan secret token
@jkh52 jkh52 closed this as not planned Won't fix, can't repro, duplicate, stale Nov 30, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness.
Projects
None yet
Development

No branches or pull requests

6 participants