Search Options

Results per page
Sort
Preferred Languages
Advance

Results 1 - 2 of 2 for monitorNodeHealth (0.17 sec)

  1. pkg/controller/nodelifecycle/node_lifecycle_controller_test.go

    		nodeIterations            []nodeIteration
    		expectedPodStatusUpdates  int
    	}{
    		// Node created long time ago, with status updated by kubelet exceeds grace period.
    		// First monitorNodeHealth check will update pod status to NotReady.
    		// Second monitorNodeHealth check will do no updates (no retry).
    		{
    			desc: "successful pod status update, no retry required",
    			fakeNodeHandler: &testutil.FakeNodeHandler{
    Registered: Sat Jun 15 01:39:40 UTC 2024
    - Last Modified: Mon Feb 26 03:26:45 UTC 2024
    - 119K bytes
    - Viewed (0)
  2. pkg/controller/nodelifecycle/node_lifecycle_controller.go

    	retrySleepTime   = 20 * time.Millisecond
    	nodeNameKeyIndex = "spec.nodeName"
    	// podUpdateWorkerSizes assumes that in most cases pod will be handled by monitorNodeHealth pass.
    	// Pod update workers will only handle lagging cache pods. 4 workers should be enough.
    	podUpdateWorkerSize = 4
    	// nodeUpdateWorkerSize defines the size of workers for node update or/and pod update.
    Registered: Sat Jun 15 01:39:40 UTC 2024
    - Last Modified: Sat May 04 18:33:12 UTC 2024
    - 51.6K bytes
    - Viewed (0)
Back to top