From cfaa1732a3839e346b64f79cd755c5b06d767d4b Mon Sep 17 00:00:00 2001 From: Neeraj Krishna Gopalakrishna Date: Thu, 15 Jan 2026 11:34:03 +0530 Subject: [PATCH] Fixes the issue in the test TestKubeletConfigMaxPods when AutoNodeSizing is enabled by default --- test/e2e-2of2/kubeletcfg_test.go | 10 ---------- 1 file changed, 10 deletions(-) diff --git a/test/e2e-2of2/kubeletcfg_test.go b/test/e2e-2of2/kubeletcfg_test.go index 968316cc09..e02404b38f 100644 --- a/test/e2e-2of2/kubeletcfg_test.go +++ b/test/e2e-2of2/kubeletcfg_test.go @@ -162,16 +162,6 @@ func runTestWithKubeletCfg(t *testing.T, testName string, regexKey []string, str } } - // Get the new node object which should reflect new values for the allocatables - if *kc1.Spec.AutoSizingReserved { - refreshedNode := helpers.GetSingleNodeByRole(t, cs, poolName) - - // The value for the allocatable should have changed because of the auto node sizing. - // We cannot predict if the values of the allocatables will increase or decrease, - // as it depends on the configuration of the system under test. - require.NotEqual(t, refreshedNode.Status.Allocatable.Memory().Value(), node.Status.Allocatable.Memory().Value(), "value of the allocatable should have changed") - } - if kc2 != nil { // create our second kubelet config and attach it to our created node pool cleanupKcFunc2 := createKcWithConfig(t, cs, kcName2, poolName, &kc2.Spec, "1")