How to fix ExcludedResourceWarning Resource /Application is excluded in the settings in Kubernetes

Check the argocd-cm ConfigMap to see what is excluded:

kubectl get configmap argocd-cm -n argocd -o yaml | grep -A 20 resource.exclusions

Common exclusions include ServiceAccount, Secret, ResourceQuota, and NetworkPolicy for security.

Use ArgoCD UI to see which resources are excluded. Go to the Application details and check the Resource Tree tab. Resources marked as excluded will show a warning icon.

To allow specific excluded resources in your application, add the IgnoreExtraneous sync option:

apiVersion: argoproj.io/v1alpha1
kind: Application
spec:
  syncPolicy:
    syncOptions:
    - RespectIgnoreDifferences=true

Or use annotations on resources to exclude them from diff detection.

To allow a specific resource type globally, edit the ConfigMap:

kubectl edit configmap argocd-cm -n argocd

Add resource.inclusions to override exclusions:

resource.inclusions: |
  - apiGroups:
    - apps
    kinds:
    - Deployment

To stop excluding a resource type entirely, edit argocd-cm and remove it from resource.exclusions:

resource.exclusions: |
  - apiGroups:
    - rbac.authorization.k8s.io
    kinds:
    - ClusterRoleBinding

When using the App of Apps pattern, the Application CRD itself must not be excluded. If it is, add it to inclusions:

resource.inclusions: |
  - apiGroups:
    - argoproj.io
    kinds:
    - Application

For production, enable RBAC-aware exclusions in argocd-cm:

resource.respectRBAC: "strict"

This ensures resources are only excluded if the service account does not have permissions.

Use cluster comparison options to handle excluded resources more carefully:

resource.customizations.comparison.rules: |
  - kinds:
    - Secret
    jqFilter: .