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-forward for UDP #47862

Open
pavolloffay opened this issue Jun 21, 2017 · 37 comments

Comments

@pavolloffay
Copy link
Contributor

commented Jun 21, 2017

Kubernetes currently supports port forwarding only for TCP ports. However, Pod/service might expose UDP port too.

@k8s-github-robot

This comment has been minimized.

Copy link
Contributor

commented Jun 21, 2017

@pavolloffay There are no sig labels on this issue. Please add a sig label by:
(1) mentioning a sig: @kubernetes/sig-<team-name>-misc
(2) specifying the label manually: /sig <label>

Note: method (1) will trigger a notification to the team. You can find the team list here and label list here

@pavolloffay

This comment has been minimized.

Copy link
Contributor Author

commented Jun 21, 2017

@kubernetes/sig-network @kubernetes/sig-node

@kargakis

This comment has been minimized.

Copy link
Member

commented Jun 21, 2017

/sig network

@cmluciano

This comment has been minimized.

Copy link
Member

commented Jun 22, 2017

/assign

@pavolloffay UDP is supported in services. Are you looking for a kubectl port-forward command?

@pavolloffay

This comment has been minimized.

Copy link
Contributor Author

commented Jun 22, 2017

@cmluciano yes kubectl port-forward pod-name udp-port

@pavolloffay

This comment has been minimized.

Copy link
Contributor Author

commented Jun 28, 2017

@cmluciano do you have any news on this? Is it in the roadmap or I was doing something wrong?

@cmluciano

This comment has been minimized.

Copy link
Member

commented Jun 28, 2017

@cmluciano

This comment has been minimized.

Copy link
Member

commented Jun 28, 2017

/area kubectl

@kargakis

This comment has been minimized.

Copy link
Member

commented Jun 28, 2017

@cmluciano why is this labeled for sig-apps? I thought port-forwarding is under the purview of network and node sigs, and the fact that there are kubectl changes that need to be made may include cli?

/remove-sig apps
/sig cli

@k8s-ci-robot k8s-ci-robot added sig/cli and removed sig/apps labels Jun 28, 2017

@cmluciano

This comment has been minimized.

Copy link
Member

commented Jun 28, 2017

That is true @kargakis . I keep forgetting that sig/cli is a thing.

@cmluciano cmluciano removed their assignment Jul 6, 2017

@cmluciano

This comment has been minimized.

Copy link
Member

commented Jul 6, 2017

@shiywang

This comment has been minimized.

Copy link
Member

commented Jul 7, 2017

/assign
I will take a look.

@pavolloffay

This comment has been minimized.

Copy link
Contributor Author

commented Jul 19, 2017

Is there any progress on this? cc @shiywang

@shiywang

This comment has been minimized.

Copy link
Member

commented Aug 1, 2017

@pavolloffay working on it right now

@resouer resouer added the sig/node label Aug 1, 2017

@resouer

This comment has been minimized.

Copy link
Member

commented Aug 1, 2017

cc @freehan you may be interested.

@ahmetb

This comment has been minimized.

Copy link
Member

commented Nov 10, 2017

Any updates @pavolloffay ? I just needed this as well.

@fejta-bot

This comment has been minimized.

Copy link

commented Feb 9, 2018

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

@fejta-bot

This comment has been minimized.

Copy link

commented Mar 11, 2018

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

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 rotten
/remove-lifecycle stale

@shiywang

This comment has been minimized.

Copy link
Member

commented Mar 11, 2018

@pavolloffay do you still need this feature? I already submit my pr and design proposal couple month ago, but seems there're some blockers here: kubernetes/community#1575 (comment), kubernetes/community#1575 (comment)

@pavolloffay

This comment has been minimized.

Copy link
Contributor Author

commented Mar 12, 2018

Yes, I would like to use it if it is realistic to implement it. There is also some interest from other users see the first comment.

@shiywang

This comment has been minimized.

Copy link
Member

commented Mar 13, 2018

/remove-lifecycle rotten

@clouless

This comment has been minimized.

Copy link

commented Jun 3, 2018

I would also love to see UDP Port Forwarding happen :)

@fejta-bot

This comment has been minimized.

Copy link

commented Sep 1, 2018

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

@fejta-bot

This comment has been minimized.

Copy link

commented Oct 1, 2018

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

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 rotten

@ecdemis123

This comment has been minimized.

Copy link

commented Oct 5, 2018

Us at Dave.com are also interested in having this feature

@qianweicheng

This comment has been minimized.

Copy link

commented Oct 10, 2018

looking forward to this feature

@mindw

This comment has been minimized.

Copy link

commented Oct 15, 2018

/remove-lifecycle rotten

Please :)

@kiefersmith

This comment has been minimized.

Copy link

commented Oct 17, 2018

Would be nice to have this!

@jmikon7

This comment has been minimized.

Copy link

commented Oct 18, 2018

We're really need this feature.

@nogoegst

This comment has been minimized.

Copy link

commented Oct 18, 2018

hey there!
is there an option to unrot an issue by a github reaction? having endless and useless comments like '+1'/'need this too' is a bit of annoying.

@dims

This comment has been minimized.

Copy link
Member

commented Oct 18, 2018

long-term-issue (note to self)

@shiywang

This comment has been minimized.

Copy link
Member

commented Oct 24, 2018

I have a proposal here: kubernetes/community#1575 and WIP pr #57441 the only blocker here is IIUC we want to remove proxying from the apiserver first.

@BenTheElder

This comment has been minimized.

Copy link
Member

commented Nov 12, 2018

/lifecycle frozen
this will not rot now, and I think this is clearly a long-term issue that needs to be taken up eventually.

regarding unrot via reaction: please file a bug with kubernetes/test-infra to discuss, IIRC it's due to the github API not considering reactions as a last-updated time.

@kfox1111

This comment has been minimized.

Copy link

commented May 11, 2019

Just tried to do this and found it doesn't work. This would be a useful feature.

@BrianMWest

This comment has been minimized.

Copy link

commented Jun 19, 2019

Also still interested in this! Very desirable functionality

@dvdbot

This comment has been minimized.

Copy link

commented Jun 28, 2019

Can't wait for this to be implemented - just needed this...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.