英文:
Troubleshooting Ingress stuck in "Progressing" state in ArgoCD
问题
我在OpenShift上运行着ArgoCD，其中一个Ingress一直处于“Progressing”状态已经有一段时间了。我可以在哪里检查以确定是否仍在进行任何进展，或者它卡在了什么地方？当ArgoCD没有报告错误时，我该如何进行故障排除？
英文:
I've got ArgoCD running on OpenShift, and one Ingress it's trying to sync has been stuck in "Progressing" for quite a while now. Is there anywhere I can check to determine whether any progress is still being made, or what it's stuck on? How can I troubleshoot when ArgoCD reports no errors?
答案1
得分: 3
我遇到了相同的问题。
请查看GitHub上的此线程。
正如之前的评论者所提到的，进展状态是由Ingress实现引起的。而Argo本身在这个问题上确实缺乏可见性。更多详细信息在此评论中有解释。
英文:
I've faced with the same issue.
Please check this thread on github.
Just as a previous commenter mentioned, progressing status is caused by ingress implementation. Argo, in its turn, really lacks visibility on this matter. There are more details explained in this comment.
答案2
得分: -1
因为 ingress 服务的 status.loadBalancer.ingress 数据为空。尝试使用 LoadBalancer 服务类型。
英文:
because status.loadBalancer.ingress data of ingress svc is empty. try use LoadBalancer svc type
通过集体智慧和协作来改善编程学习和解决问题的方式。致力于成为全球开发者共同参与的知识库，让每个人都能够通过互相帮助和分享经验来进步。
评论