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

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

Abierto
#1,663 1 comentario 1 reacción 0 asignados Ver en GitHub
Lenguaje dominante
Python
Estrellas
911
Forks
234
Merge medio
1 d 11 h
PR fusionados (30 d)
62

Descripción

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.

Guía de contribución

Abrir la guía de contribución

Evaluación

Este issue todavía no se ha evaluado.

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.