fix: use ingress subdomain instead of ipv4 to better reflect usage

Signed-off-by: Devin Buhl <devin@buhl.casa>

kubernetes/apps/networking/cloudflared/app/configs/config.yaml

@@ -10,9 +10,9 @@ ingress:
   - hostname: "${SECRET_DOMAIN}"
     service: https://ingress-nginx-controller.networking.svc.cluster.local:443
     originRequest:
-      originServerName: "ipv4.${SECRET_DOMAIN}"
+      originServerName: "ingress.${SECRET_DOMAIN}"
   - hostname: "*.${SECRET_DOMAIN}"
     service: https://ingress-nginx-controller.networking.svc.cluster.local:443
     originRequest:
-      originServerName: "ipv4.${SECRET_DOMAIN}"
+      originServerName: "ingress.${SECRET_DOMAIN}"
   - service: http_status:404

kubernetes/apps/networking/cloudflared/app/dnsendpoint.yaml

@@ -5,9 +5,9 @@ metadata:
   name: cloudflared
   namespace: networking
   annotations:
-    external-dns.alpha.kubernetes.io/target: "ipv4.${SECRET_DOMAIN}"
+    external-dns.alpha.kubernetes.io/target: "ingress.${SECRET_DOMAIN}"
 spec:
   endpoints:
-    - dnsName: "ipv4.${SECRET_DOMAIN}"
+    - dnsName: "ingress.${SECRET_DOMAIN}"
       recordType: CNAME
       targets: ["${SECRET_CLOUDFLARE_TUNNEL_ID}.cfargotunnel.com"]