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

Need a common HostPort pool across Pods and Services #1486

Closed
thockin opened this issue Sep 29, 2014 · 3 comments
Closed

Need a common HostPort pool across Pods and Services #1486

thockin opened this issue Sep 29, 2014 · 3 comments
Labels
sig/network Categorizes an issue or PR as relevant to SIG Network.

Comments

@thockin
Copy link
Member

thockin commented Sep 29, 2014

Both Pods and Services can use HostPorts. We currently check Pods against other Pods for host-port conflicts, but we do not check Pods against Services, nor vice-versa, nor Services against Services.

Even after ip-per-service, some Services will have to use HostPorts (for External Load Balancer, for now). Much reduced, but that just makes a conflict even less common and harder to debug.

We need some common way for both resource classes to check for conflicts and reserve HostPorts atomically.

@bgrant0607 bgrant0607 added the sig/network Categorizes an issue or PR as relevant to SIG Network. label Sep 30, 2014
@bgrant0607
Copy link
Member

How is this different from #974?

@thockin
Copy link
Member Author

thockin commented Sep 30, 2014

Ahh, you're right, a lot of overlap. Will de-dup.

On Mon, Sep 29, 2014 at 5:04 PM, bgrant0607 notifications@github.com
wrote:

How is this different from #974
#974?

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

@thockin
Copy link
Member Author

thockin commented Sep 30, 2014

Dup of #974

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
sig/network Categorizes an issue or PR as relevant to SIG Network.
Projects
None yet
Development

No branches or pull requests

3 participants