agentic-community / agentic-community/mcp-gateway-registry

ArgoCD + post-install hook creates a circular dependency for keycloak-client-secret (bug/design gap)

未关闭
#1,663 1 条评论 1 个 reaction 已指派 0 人 在 GitHub 查看
主要语言
Python
星标
911
派生
234
平均合并
1 天 11 小时
30 天内合并 PR
62

描述

registry/auth-server can't start without keycloak-client-secret, which is only created by the setup-keycloak post-install Helm hook Job. Under ArgoCD (which translates Helm hooks to its own PostSync phase, gated on all Sync-phase resources — including the app's own Ingress — reporting Healthy first), this creates a genuine deadlock: Ingress health depends on the pod running, the pod can't run without the secret, and the secret-creating hook won't run until Ingress is healthy. Worth flagging as an ArgoCD compatibility issue, since ArgoCD is one of the most common GitOps tools this chart would be deployed with.

贡献指南

打开贡献指南

评估

这个 Issue 还没有评估数据。

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。