kubernetes 如何处理没有任何资源配额的 pods？
How pods without any resource quota are handled by kubernetes?
如果我们在kubernetes中不申请任何资源配额，一个pod分配了多少cpu和内存资源？
当我们扩展 up/down 我们的部署时，它们是如何改变的？
我尝试阅读 kubernetes 文档，但无法找到上述答案。
我正在使用 amazon-eks。
If you do not specify a memory limit for a Container, one of the
following situations applies:
The Container has no upper bound on the amount of memory it uses. The
Container could use all of the memory available on the Node where
it is running.
The Container is running in a namespace that has a default memory limit, and the Container is automatically assigned the default limit.
Cluster administrators can use a LimitRange to specify a default value
for the memory limit.
https://kubernetes.io/docs/tasks/configure-pod-container/assign-memory-resource/
If you do not specify a CPU limit for a Container, then one of these
situations applies:
The Container has no upper bound on the CPU resources it can use. The Container could use all of the CPU resources available on the Node
where it is running.
The Container is running in a namespace that has a default CPU limit, and the Container is automatically assigned the default limit.
Cluster administrators can use a LimitRange to specify a default value
for the CPU limit.
https://kubernetes.io/docs/tasks/configure-pod-container/assign-cpu-resource/
如果我们在kubernetes中不申请任何资源配额，一个pod分配了多少cpu和内存资源？ 当我们扩展 up/down 我们的部署时，它们是如何改变的？ 我尝试阅读 kubernetes 文档，但无法找到上述答案。 我正在使用 amazon-eks。
If you do not specify a memory limit for a Container, one of the following situations applies:
The Container has no upper bound on the amount of memory it uses. The Container could use all of the memory available on the Node where it is running.
The Container is running in a namespace that has a default memory limit, and the Container is automatically assigned the default limit. Cluster administrators can use a LimitRange to specify a default value for the memory limit.
https://kubernetes.io/docs/tasks/configure-pod-container/assign-memory-resource/
If you do not specify a CPU limit for a Container, then one of these situations applies:
The Container has no upper bound on the CPU resources it can use. The Container could use all of the CPU resources available on the Node where it is running.
The Container is running in a namespace that has a default CPU limit, and the Container is automatically assigned the default limit. Cluster administrators can use a LimitRange to specify a default value for the CPU limit.
https://kubernetes.io/docs/tasks/configure-pod-container/assign-cpu-resource/