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

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

Open
#1,663 1 comment 1 reaction 0 assignees View on GitHub
Dominant language
Python
Stars
911
Forks
234
Avg merge
1d 11h
Merged PRs (30d)
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.

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.