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

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

Ouverte
#1,663 1 commentaire 1 réaction 0 personnes assignées Voir sur GitHub
Langage dominant
Python
Étoiles
911
Forks
234
Merge moyen
1 j 11 h
PR mergées (30 j)
62

Description

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.

Guide de contribution

Ouvrir le guide de contribution

Évaluation

Cette issue n'a pas encore été évaluée.

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.