Skip to content

Insufficient pods stops scaling-in confusing message-AWS EKS #1576

@prageethw

Description

@prageethw

logs below

I0113 03:43:30.105993 1 cluster.go:222] Evaluation ip-192-168-75-46.us-east-2.compute.internal for test/tiller-deploy-7b584bf689-vzbn4 -> PodFitsResources predicate mismatch, reason: Insufficient pods
I0113 03:43:30.106018 1 cluster.go:222] Evaluation ip-192-168-84-242.us-east-2.compute.internal for test/tiller-deploy-7b584bf689-vzbn4 -> PodFitsResources predicate mismatch, reason: Insufficient pods
I0113 03:43:30.106038 1 cluster.go:222] Evaluation ip-192-168-50-191.us-east-2.compute.internal for test/tiller-deploy-7b584bf689-vzbn4 -> PodFitsResources predicate mismatch, reason: Insufficient pods
I0113 03:43:30.106085 1 cluster.go:222] Evaluation ip-192-168-41-162.us-east-2.compute.internal for test/tiller-deploy-7b584bf689-vzbn4 -> PodFitsResources predicate mismatch, reason: Insufficient pods
I0113 03:43:30.106106 1 cluster.go:126] Fast evaluation: node ip-192-168-2-214.us-east-2.compute.internal is not suitable for removal: failed to find place for test/tiller-deploy-7b584bf689-vzbn4

Metadata

Metadata

Assignees

No one assigned

    Labels

    lifecycle/rottenDenotes an issue or PR that has aged beyond stale and will be auto-closed.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions