Repository navigation
Conversation
… runs About one t3a.medium in a few thousand never joins. The 5000-node runs already tolerate two; the correctness scenario keeps zero because the e2e suite waits for every node. Signed-off-by: Davanum Srinivas <davanum@gmail.com>
experiments/enable_restart_count_check.yaml is passed after overrides.yaml and wins, so the check has always been on for AWS performance runs. Signed-off-by: Davanum Srinivas <davanum@gmail.com>
kubernetes-prow
Bot
added
size/XS
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
|
@dims: The following test failed, say
Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here. |
About one t3a.medium in a few thousand never joins (containerd
can't find shim for sandbox, ci-kubernetes-e2e-ec2-scale-performance-golang-tip-500, 2026-10-27). The 5000-node runs already tolerate two. The correctness scenario keeps zero because the e2e suite waits for every node.Second commit drops the dead
ENABLE_RESTART_COUNT_CHECK: falseline:experiments/enable_restart_count_check.yamlis passed later and wins, so the check has always been on for AWS performance runs. It caught the LB controller crash loop on 2026-10-23, so it stays on.AI assisted with the triage and the patch.