This website uses cookies to ensure you get the best experience.
Learn more.
A namespace quota caps total requested CPU. A new Pod's request would exceed the remaining quota even though a node has spare CPU. What should the developer expect?
Published
- Admission can reject the Pod because namespace quota is exceeded
- The Service scales itself to cover the excess request
- The Pod receives free additional quota from another namespace
- The scheduler automatically ignores namespace quotas
Comments — 0
Sign in to comment