From c6a67b8662bb3c6efbe912b19699ace19e70dd3f Mon Sep 17 00:00:00 2001
From: Andrey Smirnov <andrey.smirnov@talos-systems.com>
Date: Thu, 18 Nov 2021 18:39:01 +0300
Subject: [PATCH] fix: ignore not existing nodes on cordoning

Fixes #4557

When running `reset` for a node which was already deleted from
Kubernetes, we should ignore failure to cordon and proceed with other
actions.

Signed-off-by: Andrey Smirnov <andrey.smirnov@talos-systems.com>
---
 pkg/kubernetes/kubernetes.go | 5 +++++
 1 file changed, 5 insertions(+)

diff --git a/pkg/kubernetes/kubernetes.go b/pkg/kubernetes/kubernetes.go
index 59e306492..6e96d3d24 100644
--- a/pkg/kubernetes/kubernetes.go
+++ b/pkg/kubernetes/kubernetes.go
@@ -348,6 +348,11 @@ func (h *Client) Cordon(ctx context.Context, name string) error {
 				return retry.ExpectedError(err)
 			}
 
+			if apierrors.IsNotFound(err) {
+				// node not found, should have already been deleted, skip cordoning
+				return nil
+			}
+
 			return err
 		}