Removes deletion timestamp check in Autocreation of TektonConfig

If TektonConfig has a deletion stamp, it won't be deleted unless the operator is up and running as the object has finalizer. waiting for it to get deleted will stop operator from running and object still won't be deleted. hence removing the condition for checking deletion timestamp and letting user to create a new instance of tektonconfig after deletion. Signed-off-by: Shivam Mukhade <[email protected]>
tektoncd · Sep 24, 2021 · 27b712d · 27b712d
1 parent 2bed57e
commit 27b712d
Showing 1 changed file with 0 additions and 5 deletions.
diff --git a/pkg/reconciler/shared/tektonconfig/instance.go b/pkg/reconciler/shared/tektonconfig/instance.go
@@ -75,11 +75,6 @@ func (tc tektonConfig) ensureInstance(ctx context.Context) {
 			OperatorV1alpha1().
 			TektonConfigs().Get(context.TODO(), DefaultCRName, metav1.GetOptions{})
 		if err == nil {
-			if !instance.GetDeletionTimestamp().IsZero() {
-				// log deleting timestamp error and retry
-				logger.Errorf("deletionTimestamp is set on existing Tektonconfig instance, Name: %w", instance.GetName())
-				return false, nil
-			}
 			return true, nil
 		}
 		if !apierrs.IsNotFound(err) {