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.

Sign up for GitHub

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

Jump to bottom

Kubernetes Proxy only supports TCP #1205

Closed
3 tasks
jbeda opened this issue Sep 6, 2014 · 6 comments · Fixed by #1273
Closed
3 tasks

Kubernetes Proxy only supports TCP #1205

jbeda opened this issue Sep 6, 2014 · 6 comments · Fixed by #1273
Assignees
@thockin
Labels
sig/network Categorizes an issue or PR as relevant to SIG Network.

Comments

@jbeda
Copy link
Contributor

jbeda commented Sep 6, 2014

We should:

  • have a protocol entry on the service that defaults to TCP
  • throw an error if users specify anything else
  • consider supporting UDP. Figuring out how to do simple load balancing and 'connection' tracking is a little tricky but solvable.

Context: https://twitter.com/bketelsen/status/508307110254608384
@smarterclayton
Copy link
Contributor

protocols: [...] if we think this could ever be something more than UDP and tcp.

@jbeda
Copy link
Contributor Author

jbeda commented Sep 7, 2014

Why not multiple ports then? We need to figure the scope of the service
object. The services v2 issue touches on some of this.

@smarterclayton
Copy link
Contributor

Ack - tcp+udp can be same port, as can tcp+http or tls+https+websockets. Should tie decisions like that in to v2

@jbeda jbeda mentioned this issue Sep 7, 2014
Closed
@thockin
Copy link
Member

thockin commented Sep 8, 2014

I'd much rather KISS and say that if you need two protocols, you need two
services. We can revisit later if that turns into a hardship

On Sun, Sep 7, 2014 at 10:17 AM, Clayton Coleman notifications@github.com
wrote:

Ack - tcp+udp can be same port, as can tcp+http or tls+https+websockets.
Should tie decisions like that in to v2

Reply to this email directly or view it on GitHub
#1205 (comment)
.

@smarterclayton
Copy link
Contributor

Point taken

@lavalamp
Copy link
Member

lavalamp commented Sep 8, 2014

If you need two protocols, you need two services.

+1

@bgrant0607 bgrant0607 added enhancement sig/network Categorizes an issue or PR as relevant to SIG Network. labels Sep 8, 2014
@brendandburns brendandburns added this to the v0.5 milestone Sep 9, 2014
@thockin thockin self-assigned this Sep 9, 2014
@brendandburns brendandburns mentioned this issue Sep 9, 2014
Closed
@thockin thockin mentioned this issue Sep 11, 2014
Merged
b3atlesfan pushed a commit to b3atlesfan/kubernetes that referenced this issue Feb 5, 2021
@rajatchopra
Merge pull request kubernetes#1205 from andreek/e2e-fix
07dc5aa 
Fix: prevent e2e tests to reuse network config of previous tests
josefkarasek pushed a commit to josefkarasek/kubernetes that referenced this issue May 5, 2022
@openshift-merge-robot
Merge pull request kubernetes#1205 from rphillips/backports/108337_4.7
0d60930 
[release-4.7] Bug 2060528: Backport inotify patch to 4.7
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@thockin thockin

Labels
sig/network Categorizes an issue or PR as relevant to SIG Network.
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Proxy udp thockin/kubernetes
6 participants
@jbeda @lavalamp @smarterclayton @thockin @brendandburns @bgrant0607