<p>I am trying to run <code>argocd</code> on my EC2 instance running <code>centos 7</code> by following <a href="https://argoproj.github.io/argo-cd/getting_started/" rel="nofollow noreferrer">official documentation</a> and <a href="https://www.eksworkshop.com/intermediate/290_argocd/install/" rel="nofollow noreferrer">EKS workshop from AWS</a>, but it is in pending state, all pods from <code>kube-system</code> namespace are running fine.</p>
<p>below is the output of <code>kubectl get pods --all-namespaces</code></p>
<pre><code>NAMESPACE     NAME                                                              READY   STATUS    RESTARTS   AGE
argocd        argocd-application-controller-5785f6b79-nvg7n                     0/1     Pending   0          29s
argocd        argocd-dex-server-7f5d7d6645-gprpd                                0/1     Pending   0          19h
argocd        argocd-redis-cccbb8f7-vb44n                                       0/1     Pending   0          19h
argocd        argocd-repo-server-67ddb49495-pnw5k                               0/1     Pending   0          19h
argocd        argocd-server-6bcbf7997d-jqqrw                                    0/1     Pending   0          19h
kube-system   calico-kube-controllers-56b44cd6d5-tzgdm                          1/1     Running   0          19h
kube-system   calico-node-4z9tx                                                 1/1     Running   0          19h
kube-system   coredns-f9fd979d6-8d6hm                                           1/1     Running   0          19h
kube-system   coredns-f9fd979d6-p9dq6                                           1/1     Running   0          19h
kube-system   etcd-ip-10-1-3-94.us-east-2.compute.internal                      1/1     Running   0          19h
kube-system   kube-apiserver-ip-10-1-3-94.us-east-2.compute.internal            1/1     Running   0          19h
kube-system   kube-controller-manager-ip-10-1-3-94.us-east-2.compute.internal   1/1     Running   0          19h
kube-system   kube-proxy-tkp7k                                                  1/1     Running   0          19h
kube-system   kube-scheduler-ip-10-1-3-94.us-east-2.compute.internal            1/1     Running   0          19h
</code></pre>
<p>While same configuration is working fine on my local mac, I've made sure that <code>docker</code>, <code>kubernetes</code> services are up and runnning. Tried deleting pods, reconfigured argocd, however everytime result remained same.</p>
<p>Being new to <code>ArgoCD</code> I am unable to figure out the reason for the same. Please let me know where I am going wrong. Thanks!</p>

Shubham Namdeo
<p>I figured out what the problem was by running:</p>
<pre><code>kubectl describe pods &lt;name&gt;  -n argocd
</code></pre>
<p>It gave output ending with FailedScheduling:</p>
<pre><code>...
Events:
  Type     Reason            Age                From               Message
  ----     ------            ----               ----               -------
  Warning  FailedScheduling  3m (x5 over 7m2s)  default-scheduler  0/1 nodes are available: 1 node(s) had taint {node-role.kubernetes.io/master: }, that the pod didn't tolerate.
</code></pre>
<p>henceforth, by referring <a href="https://github.com/calebhailey/homelab/issues/3" rel="nofollow noreferrer">this GitHub issue</a>, I figured out to run:</p>
<pre><code>kubectl taint nodes --all node-role.kubernetes.io/master-
</code></pre>
<p>After this command, pods started to work and transitioned from <code>Pending</code> state to <code>Running</code> with <code>kubectl describe pods</code> showing output as:</p>
<pre><code>...
Events:
  Type     Reason            Age                From               Message
  ----     ------            ----               ----               -------
  Warning  FailedScheduling  3m (x5 over 7m2s)  default-scheduler  0/1 nodes are available: 1 node(s) had taint {node-role.kubernetes.io/master: }, that the pod didn't tolerate.
  Normal   Scheduled         106s               default-scheduler  Successfully assigned argocd/argocd-server-7d44dfbcc4-qfj6m to ip-XX-XX-XX-XX.&lt;region&gt;.compute.internal
  Normal   Pulling           105s               kubelet            Pulling image &quot;argoproj/argocd:v1.7.6&quot;
  Normal   Pulled            81s                kubelet            Successfully pulled image &quot;argoproj/argocd:v1.7.6&quot; in 23.779457251s
  Normal   Created           72s                kubelet            Created container argocd-server
  Normal   Started           72s                kubelet            Started container argocd-server
</code></pre>
<p>From this error and resolution I've learned to always use <code>kubectl describe pods</code> to resolve the errors.</p>
