This repository was archived by the owner on Sep 24, 2025. It is now read-only.
Fix: Handle Deleted Namespaces Gracefully During Sync #785
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Fix infinite sync failure loops when managed namespaces are deleted by implementing automatic namespace validation and cleanup during cluster cache synchronization.
Fixes: argoproj/argo-cd#24709
Problem
When namespaces managed by ArgoCD are deleted without first removing the
managed-by
label, the GitOps Engine enters an infinite failure loop during cluster cache sync operations. TheprocessApi()
function attempts to list resources in deleted namespaces, resulting in 403 Forbidden errors from the Kubernetes API. This causes:Root Cause: The
sync()
process iterates throughc.namespaces
slice containing deleted namespace names but has no validation to check if those namespaces still exist before attempting API operations.Solution
Implement namespace validation with automatic cleanup:
Key Changes
namespaceExists()
function - Validates namespace existence using canonicalapierrors.IsNotFound()
detectionprocessApi()
- Skip deleted namespaces during resource processing using thread-safe trackingsync()
- Remove deleted namespaces from configuration after parallel processing completesI also added a test for the scenario called
TestSyncWithDeletedNamespace
and added the default namespace in other tests to not break them.