无法使ArgoCD在运行centos 7的EC2上工作

问题描述

我尝试通过遵循official documentation和EKS workshop from AWS在运行argocd的EC2实例上运行centos 7，但是它处于待处理状态，来自{{1 }}名称空间运行正常。

下面是kube-system

的输出

kubectl get pods --all-namespaces

虽然相同的配置在我的本地Mac上运行正常，但我已确保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 ，docker服务已启动并正在运行。尝试删除Pod，重新配置了argocd，但是每次结果都保持不变。

kubernetes的新手，我无法弄清楚原因。请让我知道我要去哪里了。谢谢！

解决方法

我通过运行找出了问题所在：

kubectl describe pods <name>  -n argocd

它给出了以FailedScheduling结尾的输出：

...
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.

此后，通过引用this GitHub issue，我发现可以运行：

kubectl taint nodes --all node-role.kubernetes.io/master-

此命令之后，广告连播开始工作，并从Pending状态转换为Running，其中kubectl describe pods的输出显示为：

...
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.<region>.compute.internal
  Normal   Pulling           105s               kubelet            Pulling image "argoproj/argocd:v1.7.6"
  Normal   Pulled            81s                kubelet            Successfully pulled image "argoproj/argocd:v1.7.6" in 23.779457251s
  Normal   Created           72s                kubelet            Created container argocd-server
  Normal   Started           72s                kubelet            Started container argocd-server

从这种错误和解决方案中，我学会了始终使用kubectl describe pods来解决错误。