MijnBureau installation — remaining issues and follow-up

This document records the remaining issues and recommended follow-up after deploying MijnBureau (demo, nano-oriented overlay, OVERLAY_VERSION=7) to namespace mijnbureau on the Talos/Kubernetes homelab cluster via ArgoCD + Helmfile CMP.

Status snapshot (end of run): core Deployments/StatefulSets and application workloads are running/ready, wildcard TLS ingresses are in place, Keycloak is reachable, and the mijnbureau realm was bootstrapped manually. The ArgoCD Application is not in a clean synced/healthy state due to hook/operation failures (see below).

Remaining issues

1. ArgoCD Application sync is not clean

2. keycloak-config-cli hook not converged declaratively

3. End-to-end application/OIDC validation incomplete

4. Known/tolerated warnings and environment gaps

5. Hook/image reliability on this cluster

Follow-up actions

  1. Stabilize ArgoCD sync

    • Inspect current operation/hook failures: kubectl -n argocd get app mijn-bureau -o yaml (operation state, sync result, hook phases/messages) and related Jobs/Pods in mijnbureau.
    • Ensure required hook images are pullable/cached on all relevant nodes (or adjust hook job scheduling/image policy as appropriate).
    • Decide on a controlled reconciliation: re-run/repair failed hooks, then perform a fresh sync/app recreate with a forced render (restart repo-server and/or flush Redis / bump overlay env) only when hooks will complete cleanly.
    • Target end state: Synced and Healthy with no failing hook tasks.
  2. Make Keycloak configuration declarative again

    • Pre-pull or otherwise make adorsys/keycloak-config-cli reliably available, then run the keycloak-config-cli Job (or allow ArgoCD to run it) and confirm it completes successfully.
    • Verify realm/clients/users match the rendered config (ConfigMap/Secret: keycloak-config-cli) and that manual bootstrap did not diverge from desired state.
  3. Validate application functionality

    • Add local name resolution for *.mijnbureau.kubernetes.local to 192.168.0.192 and test via browser with the self-signed wildcard cert trusted/accepted as needed.
    • Exercise login/SSO for enabled apps (Keycloak, Element/Matrix, Docs, Drive, Projects, Calendars, Bureaublad, Conversations, Collabora) and confirm redirect/callback behavior.
    • Confirm Synapse and OIDC-dependent integrations work with the mixed browser/in-cluster endpoint configuration.
  4. Clean up and harden

    • Remove or reconcile leftover DaemonSets/Jobs/pods/artifacts no longer needed (e.g. image-prepull helpers, failed historical Jobs) after confirming they are safe to delete.
    • Revisit HPA enablement only after installing/configuring metrics-server and validating ArgoCD sync behavior.
    • Keep and review the CMP overlay/patches in /tmp/opencode/argocd-helmfile-cmp.yaml and /tmp/opencode/application-mijn-bureau.yaml; persist them in the repo/IaC if this configuration should be reproducible.
  5. Documentation

    • Keep installation-mijnbureau.md aligned with any further fixes (hook handling, image pinning/mirroring, final ArgoCD sync procedure, and validated app-specific steps).

References