From 197db592b33274a71c5d54f05ba32b60b9605701 Mon Sep 17 00:00:00 2001 From: Jonathan Innis Date: Fri, 10 May 2024 09:58:03 -0500 Subject: [PATCH] test: Fix NotFound error on upgrade (#6176) --- .github/actions/e2e/setup-cluster/action.yaml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/.github/actions/e2e/setup-cluster/action.yaml b/.github/actions/e2e/setup-cluster/action.yaml index f93f72ff4d13..1a7cf223a0a0 100644 --- a/.github/actions/e2e/setup-cluster/action.yaml +++ b/.github/actions/e2e/setup-cluster/action.yaml @@ -223,7 +223,7 @@ runs: # We delete DaemonSets that we don't care about because it causes inconsistencies in scheduling due to # dcgm-exporter and neuron-monitor selecting on specific instance types # See https://github.com/kubernetes-sigs/karpenter/issues/715 for more detail - kubectl delete daemonsets -n amazon-cloudwatch dcgm-exporter neuron-monitor + kubectl delete daemonsets -n amazon-cloudwatch dcgm-exporter neuron-monitor --ignore-not-found # We patch the priorityClass onto all DaemonSets to ensure that DaemonSets always schedule to nodes so we don't get scheduling inconsistencies # See https://karpenter.sh/docs/faq/#when-deploying-an-additional-daemonset-to-my-cluster-why-does-karpenter-not-scale-up-my-nodes-to-support-the-extra-daemonset for more detail