Argo CD Ingress Stuck – Find & Fix

Argo CD Ingress Stuck – Find & Fix When Argo CD ingress gets stuck—no ADDRESS assigned or stuck in Terminating—the AWS Load Balancer Controller may be failing to reconcile. Use the steps below to find the cause and apply fixes. 1. Overview Common causes: Stale ssl-redirect annotation without certificate-arn —ALB controller cannot create the HTTPS listener Ingress stuck in deletion —finalizers prevent removal (e.g. ingress.k8s.aws/resources ) ALB controller errors —certificate validation or security group cleanup failures What this guide does: Confirms the ingress is stuck and why (no ADDRESS or stuck in Terminating) Shows how to check for stale annotations and controller logs Removes the ssl-redirect annotation when it blocks creation Clears finalizers when the ingress is stuck in deletion 2. Prerequisites Before starting, ensure you have: kubectl configured with context set to your cluster Permissions to get, patch, and annotate resources in the argocd namespace 3. Confirm the Ingress