d33fa39abf
Automatic merge from submit-queue
AWS: Move enforcement of attached AWS device limit from kubelet to scheduler
Limit of nr. of attached EBS volumes to a node is now enforced by scheduler. It can be adjusted by `KUBE_MAX_PD_VOLS` env. variable there. Therefore we don't need the same check in kubelet. If the system admin wants to attach more, we should allow it.
Kubelet limit is now 650 attached volumes ('ba'..'zz').
Note that the scheduler counts only *pods* assigned to a node. When a pod is deleted and a new pod is scheduled on a node, kubelet start (slowly) detaching the old volume and (slowly) attaching the new volume. Depending on AWS speed **it may happen that more than KUBE_MAX_PD_VOLS volumes are actually attached to a node for some time!** Kubelet will clean it up in few seconds / minutes (both attach/detach is quite slow).
Fixes #22994
|
||
|---|---|---|
| .. | ||
| aws_instancegroups.go | ||
| aws_loadbalancer.go | ||
| aws_routes.go | ||
| aws_test.go | ||
| aws_utils.go | ||
| aws.go | ||
| log_handler.go | ||
| OWNERS | ||
| retry_handler_test.go | ||
| retry_handler.go | ||
| sets_ippermissions.go | ||