1 Answer
- Newest
- Most votes
- Most comments
0
It is Kubernetes scheduler, not EKS, that schedules the pod.
That said, because you only had one node in one zone, the scheduler did not violate your constraints.
The skew is always 0. Please refer here as to how the skew is calculated.
Cluster Autoscaler does not consider this constraint when making scaling decisions.
You might want to consider increase the minimal and desired instance in your ASG.
answered 2 years ago
Relevant content
- asked 5 months ago
- asked 9 months ago
- asked 7 months ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated a month ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated a month ago
Thank you. Is there a way to do this without having minimal / desired capacity set?