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

ResourceQuota should check NodePort services usage and limits #21677

Closed
sdminonne opened this issue Feb 22, 2016 · 0 comments · Fixed by #22154
Closed

ResourceQuota should check NodePort services usage and limits #21677

sdminonne opened this issue Feb 22, 2016 · 0 comments · Fixed by #22154
Labels
priority/backlog Higher priority than priority/awaiting-more-evidence.

Comments

@sdminonne
Copy link
Contributor

NodePort services claim a port on every node in the cluster: admin may want to limit NodePort services via quota mechanism.

As soon @derekwaynecarr #20446 will be merged I'd like to supply a PR for this.

API should be modified adding only:

// The following identify resource constants for Kubernetes object types
const (
...
    // ResourceNodePorts, number
    ResourceNodePorts ResourceName = "nodeports" 
...
)

or similar.

@thockin @bgrant0607

@bgrant0607 bgrant0607 added the priority/backlog Higher priority than priority/awaiting-more-evidence. label Feb 26, 2016
k8s-github-robot pushed a commit that referenced this issue Apr 13, 2016
Automatic merge from submit-queue

Adding nodeports services to quota

To fix #21677
@derekwaynecarr
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
priority/backlog Higher priority than priority/awaiting-more-evidence.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants