Closed PancoCheong closed 1 month ago
This issue is currently awaiting triage.
SIG Docs takes a lead on issue triage for this website, but any Kubernetes member can accept issues by applying the triage/accepted
label.
The triage/accepted
label can be added by org members by writing /triage accepted
in a comment.
/language en
110 is the default limit, you can tune it using the --max-pods (https://kubernetes.io/docs/reference/command-line-tools-reference/kubelet/) flag anyway.
There is some discussion about it. refer here
That is how Kubernetes was designed.
/kind support
We could update the page to clarify whether these are hard limits.
Improvements for this is already tracking in #42373 I am closing this support ticket and suggesting people who are checking this issue to directly refer #42373
/close
@T-Lakshmi: Closing this issue.
No more than 110 pods per node
is this a hard limit? I got a powerful hardware that uses only less than 20% of CPU and 15% of RAM, just wonder why the official document suggest not more than 110 pods. I found may post on the internet suggest we can increase this number to higher number eg. 160 is the default value on DaoCloud that use K8S as the base.
Just wonder should this pods per node settings related to the CPU and RAM resources on the server?