chengjoey

Results 90 comments of chengjoey

hotfix when a plugin (in-tree or out-of-tree) return non-existent/illegal nodes, the pod scheduling flow will abort immediately.

/test pull-kubernetes-unit-go-compatibility

hotfix when a plugin (in-tree or out-of-tree) return non-existent/illegal nodes, the pod scheduling flow will abort immediately.

> I don't think the tests are flaky. Maybe they are making some assumptions about the nodes existing. > > If it becomes too much burden to fix them, I...

hotfix when a plugin (in-tree or out-of-tree) return non-existent/illegal nodes, the pod scheduling flow will abort immediately.

> @chengjoey could you also incorporate [d382150](https://github.com/kubernetes/kubernetes/commit/d3821508f13117f9f6c9a4b3046eb7971b057d50) into this PR? done

hotfix when a plugin (in-tree or out-of-tree) return non-existent/illegal nodes, the pod scheduling flow will abort immediately.

/test pull-kubernetes-integration-go-compatibility

hotfix when a plugin (in-tree or out-of-tree) return non-existent/illegal nodes, the pod scheduling flow will abort immediately.

> The following test **failed**, say `/retest` to rerun all failed tests or `/retest-required` to rerun all mandatory failed tests: It seems that this failed test is strangely, because the...

hotfix when a plugin (in-tree or out-of-tree) return non-existent/illegal nodes, the pod scheduling flow will abort immediately.

/test pull-kubernetes-integration-go-compatibility

hotfix when a plugin (in-tree or out-of-tree) return non-existent/illegal nodes, the pod scheduling flow will abort immediately.

> Also worth cherry-picking #124567 ok there are cherry-pick lists [add integration test for pod with pvc has node-affinity to non-existent/illegal nodes](https://github.com/kubernetes/kubernetes/pull/124666) 124666 [add e2e test when a plugin (in-tree...

hotfix when a plugin (in-tree or out-of-tree) return non-existent/illegal nodes, the pod scheduling flow will abort immediately.

> @chengjoey could you update the release-note as: > > ``` > Fixed a bug that a pod may remain unscheduled if any PreFilter plugin returns nodes that do not...

hotfix when a plugin (in-tree or out-of-tree) return non-existent/illegal nodes, the pod scheduling flow will abort immediately.

After merging, need cherry-pick to 1.27 and 1.28

hotfix when a plugin (in-tree or out-of-tree) return non-existent/illegal nodes, the pod scheduling flow will abort immediately.

cherry-pick #124714 preallocation for NodeToStatusMap