feat(cloudflared): manage tunnel ingress locally via ConfigMap #69

Closed
rock wants to merge 0 commits from harness/zitadel-iam-wiring into main
Owner

The tunnel was remotely managed from the Zero Trust dashboard: the Deployment ran run --token and ignored the ConfigMap already in the tree. This switches to a locally-managed tunnel so the ingress routing table lives in git.

  • deployment: mount cloudflared-config (config.yml) and the cloudflared-credentials Secret; drop TUNNEL_TOKEN
  • configmap.yaml: per-hostname ingress rules to ingress-nginx via the CoreDNS rewrite, plus a 404 catch-all
  • secret-generator: register the SOPS-encrypted credentials file
  • homelab-ca: add the cloudflared namespace copy so the connector trusts the ingress certificate (force-ssl-redirect makes plaintext impossible)

Credentials were extracted from the live cloudflared-token Secret and re-encrypted with SOPS; no plaintext secret is committed.

Adds zitadel.riotpiao.com to the ingress list — the remotely-managed config lacked it, which is why that hostname returns 404 today.

The tunnel was remotely managed from the Zero Trust dashboard: the Deployment ran `run --token` and ignored the ConfigMap already in the tree. This switches to a locally-managed tunnel so the ingress routing table lives in git. - deployment: mount `cloudflared-config` (config.yml) and the `cloudflared-credentials` Secret; drop `TUNNEL_TOKEN` - configmap.yaml: per-hostname ingress rules to ingress-nginx via the CoreDNS rewrite, plus a 404 catch-all - secret-generator: register the SOPS-encrypted credentials file - homelab-ca: add the cloudflared namespace copy so the connector trusts the ingress certificate (`force-ssl-redirect` makes plaintext impossible) Credentials were extracted from the live `cloudflared-token` Secret and re-encrypted with SOPS; no plaintext secret is committed. Adds `zitadel.riotpiao.com` to the ingress list — the remotely-managed config lacked it, which is why that hostname returns 404 today.
rock added 1 commit 2026-10-26 03:00:24 +00:00
The tunnel was remotely managed from the Zero Trust dashboard: the
Deployment ran 'run --token' and ignored the ConfigMap that already
existed in the tree. Switch to a locally-managed tunnel so the ingress
routing table lives in git.

- deployment: mount cloudflared-config (config.yml) and the
  cloudflared-credentials Secret; drop TUNNEL_TOKEN env
- configmap.yaml: per-hostname ingress rules to ingress-nginx via the
  CoreDNS rewrite, plus a 404 catch-all
- secret-generator: register the SOPS-encrypted credentials file
- homelab-ca: add the cloudflared namespace copy so the connector trusts
  the ingress certificate (force-ssl-redirect makes plaintext impossible)

Credentials were extracted from the live cloudflared-token Secret and
re-encrypted with SOPS; no plaintext secret is committed.
rock closed this pull request 2026-10-26 03:26:52 +00:00

Pull request closed

Please reopen this pull request to perform a merge.
Sign in to join this conversation.