Change:
https://k8s- https://k8s- https://k8s- https://k8s- https://k8s- https://k8s- May 9 15:57:39.163: Unexpected no endpoints return This feels similar to issues resolved in master over the past weeks by SIG Autoscaling around HPA and metrics server. Could it be that something needs backported, perhaps the use of the new metrics server image? Or is there a latent and genuine incompatibility here? It wasn't pursued aggressively previously as the symptom overlapped with multiple other ones being worked in master. Now that they're resolved and this issue has persisted, this is likely a release blocker. /kind bug /priority failing-test /priority critical-urgent /sig apps /assign /cc /milestone v1.12
/assign /sig node
/unassign Removing myself from being assigned as I don't own the code.
/remove-sig node
is there any chance this is related to your taint nodes by condition work?
/assign not sure, let me check it anyway :)
Open to handle that. In DaemonSet upgrade e2e test, it check whether a node is schedulable by , it is not enough. Open the PR to check it by , similar to DaemonSet e2e test.
The fix was just merged. Let's keep this open until tests start passing.
I believe these two: https://k8s- (run 4267) https://k8s- (run 4946) are likely to be our next ones that give an idea of health on this topic.
https://k8s- still failed, but on a different test. I'm not seeing a reason the newly failing test would be related to the original symptom here. Also not seeing why it would suddenly have flaked. :(
The pod failed because its container cannot run: The failure doesn't seem to related to or DaemonSet in general.
https://k8s- starts passing. https://k8s- isn't passing. However, it doesn't seem to be running the updated upgrade test, given that the debug log removed in still exists: .
should we cherrypick? can not open the link because gfw right now.
I suppose cherry picking this back to 1.11 branch would allow us to at least clear up the CI signal in testgrid for things that are related. Since we have at least one other up/downgrade issue it seems still, having less noise in CI would be useful. Can you submit a PR ?
sure, opened for 1.11.
As I can see this has been passing since then. /close sidenote - daemonset-upgrade is currently only failing on https://k8s- since yesterday, together with but it seems that it's a different issue:
Closing this issue. <detailsIn response to : As I can see this has been passing since then. sidenote - https://k8s- but it seems that it's a different issue: Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details

Discussion:
nodeNames := make([]string, 0) for _, node := range nodeList.Items { <del> if len(node.Spec.Taints) == 0 { nodeNames = append(nodeNames, node.Name) } else { framework.Logf("Node %v not expected to have DaemonSet pod, has taints %v", node.Name, node.Spec.Taints) </del> <ins> if len(node.Spec.Taints) != 0 { framework.Logf("Ignore taints %v on Node %v for DaemonSet Pod.", node.Spec.Taints, node.Name) </ins> } <ins> // DaemonSet Pods are expected to run on all the nodes in e2e. nodeNames = append(nodeNames, node.Name) </ins> } return checkDaemonPodOnNodes(f, namespace, selector, nodeNames)