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

Slave pod creating will failed if the owner pod namespace enabled Resource Quotas #3

Closed
pokerfaceSad opened this issue Dec 31, 2020 · 2 comments
Labels
enhancement New feature or request

Comments

@pokerfaceSad
Copy link
Owner

Refer to the K8S documentation

If quota is enabled in a namespace for compute resources like cpu and memory, users must specify requests or limits for those values; otherwise, the quota system may reject pod creation.

So slave pod creating will be failed if the owner pod namespace enabled resource quotas.

pods "xxx" is forbidden

And if we create slave pod in the owner pod namespace by set a resource quota, the slave pod need to consume resource quotas. It is unreasonable in a multi-tenant cluster scenario.

@pokerfaceSad pokerfaceSad added the enhancement New feature or request label Dec 31, 2020
@pokerfaceSad
Copy link
Owner Author

So create the slave pod in a specify namespace without resource quota can resolve this issue.

Even though the owner pod namespace enabled resource quota, the slave pod can be created successfully and won't consume the resource quota.

@pokerfaceSad
Copy link
Owner Author

Fixed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant