Cloudflare Tunnel not working

[MrMarble]

Hello!
I have to say that I'm not directly using this template, I'm still using the configurations provided as a starting point.
I have set up cloudflared and external-dns and it should be working, but it does not.

Cloudflare marks the tunnel as healthy and external-dns seems to create the DNS entries without problem, but I can't access my services outside the network, I'm able to access on my network using Pi-Hole dnsmasq

I think I'm missing something, but can't wrap my head around it

 level=info msg="Using inCluster-config based on serviceaccount-token"
 level=info msg="Created Kubernetes client https://10.96.0.1:443"
 level=info msg="Changing record." action=CREATE record=ingress.secret_domain.xyz ttl=1 type=CNAME zone=xxxxx
 level=info msg="Changing record." action=CREATE record=k8s.ingress.secret_domain.xyz ttl=1 type=TXT zone=xxx
 level=info msg="Changing record." action=CREATE record=k8s.cname-ingress.secret_domain.xyz ttl=1 type=TXT zone=xxxx
 level=info msg="All records are already up to date"

censored tunnel id

Config files:
https://github.com/MrMarble/home-ops/tree/main/kubernetes/home-cluster/apps/networking/external-dns/app
https://github.com/MrMarble/home-ops/tree/main/kubernetes/home-cluster/apps/networking/cloudflared/app

[MrMarble]

I made some progress, noticed I still was using the annotation external-dns.io/is-public: true, changed it for external-dns.alpha.kubernetes.io/target: "ingress.${SECRET_DOMAIN}" and now in cloudflare it points to the ingress but still doesn't work

These are the logs of cloudflared

2023-07-17T14:17:25Z INF Starting tunnel tunnelID=XXXX
2023-07-17T14:17:25Z INF Version 2023.7.1
2023-07-17T14:17:25Z INF GOOS: linux, GOVersion: go1.19.11, GoArch: amd64
2023-07-17T14:17:25Z INF Settings: map[config:/etc/cloudflared/config/config.yaml no-autoupdate:true]
2023-07-17T14:17:25Z INF Environmental variables map[TUNNEL_CRED_FILE:/etc/cloudflared/creds/credentials.json TUNNEL_METRICS:0.0.0.0:8080 TUNNEL_TRANSPORT_PROTOCOL:auto]
2023-07-17T14:17:25Z INF Generated Connector ID: XXXXX
2023-07-17T14:17:25Z INF Initial protocol quic
2023-07-17T14:17:25Z INF ICMP proxy will use 10.244.0.113 as source for IPv4
2023-07-17T14:17:25Z INF ICMP proxy will use fe80::4cfb:64ff:fec7:7d39 in zone eth0 as source for IPv6
2023-07-17T14:17:25Z INF Starting metrics server on [::]:8080/metrics
2023/07/17 14:17:25 failed to sufficiently increase receive buffer size (was: 208 kiB, wanted: 2048 kiB, got: 416 kiB). See https://github.com/quic-go/quic-go/wiki/UDP-Receive-Buffer-Size for details.
2023-07-17T14:17:26Z INF Registered tunnel connection connIndex=0 connection=18c8f994-3c37-428a-a083-53ee0ed7372d event=0 ip=198.41.200.13 location=MAD protocol=quic
2023-07-17T14:17:27Z INF Registered tunnel connection connIndex=1 connection=cb36ffe7-473d-40c8-91fc-9748653e46b9 event=0 ip=198.41.192.227 location=CDG protocol=quic
2023-07-17T14:17:28Z INF Registered tunnel connection connIndex=2 connection=c9795063-4b26-4099-baef-46e2a9d1e6ca event=0 ip=198.41.192.167 location=CDG protocol=quic
2023-07-17T14:17:29Z INF Registered tunnel connection connIndex=3 connection=2e1d7705-bc4b-406e-8c65-2de99f24cbaa event=0 ip=198.41.200.23 location=MAD protocol=quic

does not change when trying to access

[MrMarble]

Manually setting the dns entry to vi proxied by cloudflare fixes the problem, why does not external-dns mark de entry as proxied?
I have configured the extra args

extra-args:
      - --cloudflare-proxied

https://github.com/MrMarble/home-ops/blob/28fff2644f1dd72cab122f656f4dbbe5105de4e5/kubernetes/home-cluster/apps/networking/external-dns/app/helm-release.yaml#L35-L39

[MrMarble]

Silly mistake, should be extraArgs not extra-args

[onedr0p]

Glad you were able to figure it out, hope you enjoy the new set up!