aws / karpenter-core / 5800176852

79%

main: 80%

Pull #450

github

fix: resolve issue interpreting preferred node affinities

We were treating preferred node affinities as required for topology
spread purposes. This would cause us to incorrectly restrict the pod's
domains to only ones that were acceptable per the preference.  In some
cases, this can lead to pods remaining pending as we assume a pod will
schedule to an existing node, but it won't due to a required topology
spread and our incorrect restriction.

31 of 31 new or added lines in 3 files covered. (100.0%)

7960 of 10024 relevant lines covered (79.41%)

177094.11 hits per line