How to fix ArgoCD missing in Kubernetes

KubernetesINTERMEDIATEHIGHUpdated Dec 6, 2025· 182 views

ArgoCD components are missing when the installation is incomplete or CRDs are not properly installed. This occurs when namespace-scoped deployments lack CustomResourceDefinitions (CRDs) or core components (API server, controller, repo server) fail to start. Fix by installing ArgoCD with all required manifests and verifying all pods are running.

Quick fix

Fixes ArgoCD missing

kubectl create namespace argocd
  1. Create the argocd namespace
  2. Install ArgoCD manifests
  3. Install Custom Resource Definitions (CRDs)
  4. Verify all pods are running
kubernetes — error
kubectl create namespace argocd
ArgoCD missing

What this error means

The ArgoCD missing error indicates that one or more critical ArgoCD components are not installed or not running in your Kubernetes cluster. ArgoCD requires several core components: the API server (for Web UI and CLI access), application controller (for managing deployments), repo server (for Git interactions), and Custom Resource Definitions (CRDs) for Application and ApplicationSet resources. When these components are missing, ArgoCD cannot function properly.

Typical symptoms

  • ArgoCD namespace exists but pods are not running or missing
  • kubectl get pods -n argocd shows fewer pods than expected
  • ArgoCD UI/server is not accessible at expected port
  • Application resources fail with "ApplicationSet not found" or similar errors
  • argocd CLI commands fail with connection refused errors
  • Events show ImagePullBackOff or CrashLoopBackOff for ArgoCD pods
  • Helm chart install completes but CRDs are not created

Common causes

  1. Installation manifest was not fully applied (using namespace-install.yaml without CRDs)
  2. ArgoCD namespace was not created before installing
  3. CRD manifests from manifests/crds directory were not installed separately
  4. Required images are not available or not pulled successfully
  5. Redis dependency failed to install or start (required for caching)
  6. Insufficient cluster resources (CPU, memory) to schedule ArgoCD pods
  7. Network policies in argocd namespace are blocking inter-pod communication
  8. Using Helm but values.yaml does not include all required components

How to fix "ArgoCD missing"

1Create the argocd namespace

First, ensure the namespace exists:

bash
kubectl create namespace argocd

If namespace already exists, this command will return an error (which is safe to ignore).

2Install ArgoCD manifests

Apply the complete ArgoCD installation manifest:

bash
kubectl apply -n argocd -f https://raw.githubusercontent.com/argoproj/argo-cd/stable/manifests/install.yaml

For namespace-scoped installation (no cluster-wide access):

bash
kubectl apply -n argocd -f https://raw.githubusercontent.com/argoproj/argo-cd/stable/manifests/namespace-install.yaml

Note: namespace-install.yaml requires manual CRD installation (see next step).

3Install Custom Resource Definitions (CRDs)

If using namespace-install.yaml, CRDs must be installed separately:

bash
kubectl apply -f https://raw.githubusercontent.com/argoproj/argo-cd/stable/manifests/crds/application-crd.yaml
kubectl apply -f https://raw.githubusercontent.com/argoproj/argo-cd/stable/manifests/crds/applicationset-crd.yaml
kubectl apply -f https://raw.githubusercontent.com/argoproj/argo-cd/stable/manifests/crds/appproject-crd.yaml

Verify CRDs are installed:

bash
kubectl get crd | grep argoproj
4Verify all pods are running

Check that all ArgoCD components are deployed and healthy:

bash
kubectl get pods -n argocd

Expected pods (multi-tenant install):
- argocd-application-controller
- argocd-applicationset-controller
- argocd-dex-server
- argocd-notifications-controller
- argocd-repo-server
- argocd-redis
- argocd-server

All pods should show status Running with 1/1 ready. If any show CrashLoopBackOff or Pending, investigate with:

bash
kubectl describe pod <pod-name> -n argocd
kubectl logs <pod-name> -n argocd
5Verify Redis is available

ArgoCD requires Redis for caching (even though controller can run without it, it's not recommended):

bash
kubectl get pod -n argocd -l app.kubernetes.io/name=argocd-redis

If redis pod is missing, apply the complete install.yaml which includes Redis deployment. If using Helm:

bash
helm repo add argo https://argoproj.github.io/argo-helm
helm install argocd argo/argo-cd -n argocd --set redis.enabled=true
6Check for network policy issues

If pods are running but cannot communicate, check for blocking network policies:

bash
kubectl get networkpolicy -n argocd

If restrictive policies exist, delete them temporarily to test:

bash
kubectl delete networkpolicy -n argocd <policy-name>

Then verify connectivity. Create new policies that allow pod-to-pod communication within the argocd namespace.

7Verify ArgoCD UI accessibility

Once all pods are running, forward the ArgoCD server port:

bash
kubectl port-forward svc/argocd-server -n argocd 8080:443

Access the UI at https://localhost:8080. Get the initial admin password:

bash
kubectl -n argocd get secret argocd-initial-admin-secret -o jsonpath="{.data.password}" | base64 -d; echo

Login with username: admin

8Use Helm for complete installation

For a cleaner, managed installation, use the official Helm chart:

bash
helm repo add argo https://argoproj.github.io/argo-helm
helm repo update
helm install argocd argo/argo-cd -n argocd --create-namespace

This ensures all required components and dependencies (including Redis, CRDs, RBAC) are installed together. Verify installation:

bash
helm status argocd -n argocd

Advanced notes

ArgoCD Core is a headless variant without API server or UI—only use if you need controller functionality without the web interface. When using namespace-scoped install, Application CRDs must be in the same namespace as ArgoCD itself. For HA deployments, consider using argo/argo-cd Helm chart with replicas and persistence enabled. If pods are evicted due to resource pressure, increase node resources or set resource limits in values.yaml. Some cloud providers (EKS, AKS, GKE) may have pre-requirements (CNI plugins, IAM roles) that must be configured before ArgoCD can fully function.

Frequently asked questions

What does "ArgoCD missing" mean?
The ArgoCD missing error indicates that one or more critical ArgoCD components are not installed or not running in your Kubernetes cluster. ArgoCD requires several core components: the API server (for Web UI and CLI access), application controller (for managing deployments), repo server (for Git interactions), and Custom Resource Definitions (CRDs) for Application and ApplicationSet resources. When these components are missing, ArgoCD cannot function properly.
How do I fix "ArgoCD missing"?
ArgoCD components are missing when the installation is incomplete or CRDs are not properly installed. This occurs when namespace-scoped deployments lack CustomResourceDefinitions (CRDs) or core components (API server, controller, repo server) fail to start. Fix by installing ArgoCD with all required manifests and verifying all pods are running.
What causes "ArgoCD missing"?
Installation manifest was not fully applied (using namespace-install.yaml without CRDs) ArgoCD namespace was not created before installing CRD manifests from manifests/crds directory were not installed separately
Is the "ArgoCD missing" error serious?
Yes. This is a high-severity error that usually blocks work until it is fixed, but the steps above resolve it.

Official resources & further reading