From 686ccceba3abc5caf9b7e61870df603e44679bfa Mon Sep 17 00:00:00 2001 From: guozheng-shen <165548992+guozheng-shen@users.noreply.github.com> Date: Mon, 9 Sep 2024 14:36:41 +0800 Subject: [PATCH] Update node_lifecycle_controller.go remove 'pod-eviction-timeout' comment --- pkg/controller/nodelifecycle/node_lifecycle_controller.go | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/pkg/controller/nodelifecycle/node_lifecycle_controller.go b/pkg/controller/nodelifecycle/node_lifecycle_controller.go index 5153aad1a68..2429f7678ed 100644 --- a/pkg/controller/nodelifecycle/node_lifecycle_controller.go +++ b/pkg/controller/nodelifecycle/node_lifecycle_controller.go @@ -270,9 +270,7 @@ type Controller struct { // Controller will not proactively sync node health, but will monitor node // health signal updated from kubelet. There are 2 kinds of node healthiness // signals: NodeStatus and NodeLease. If it doesn't receive update for this amount - // of time, it will start posting "NodeReady==ConditionUnknown". The amount of - // time before which Controller start evicting pods is controlled via flag - // 'pod-eviction-timeout'. + // of time, it will start posting "NodeReady==ConditionUnknown". // Note: be cautious when changing the constant, it must work with // nodeStatusUpdateFrequency in kubelet and renewInterval in NodeLease // controller. The node health signal update frequency is the minimal of the