--default-targets not working for Ingress resources without loadBalancer status

[lambertpandian]

Description:

External-DNS fails to create DNS records for Ingress resources when ingress.status.loadBalancer is empty, even when --default-targets and --force-default-targets flags are configured.

Expected Behavior:

When using --default-targets with --force-default-targets, External-DNS should create DNS records for Ingress resources that don't have a loadBalancer status, using the default target IP/hostname as the record target (similar to how CRD sources work).

Actual Behavior:

Ingress resources without status.loadBalancer.ingress[] entries are skipped entirely and no DNS records are created, despite having valid host rules and the --default-targets flag being set.

Configuration:

--default-targets=172.205.84.77
--force-default-targets
--source=ingress

Example Ingress:

apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
  name: example-ingress
  namespace: default
spec:
  rules:
  - host: example.example.net
    http:
      paths:
      - path: /
        pathType: Prefix
        backend:
          service:
            name: example-service
            port:
              number: 80
status: {}  # No loadBalancer status

[ivankatliarchuk]

The flag is designed specifically for DNSEndpoint.

It looks like your environment is missing an Ingress controller, and you’re trying to use an Ingress as if it were a DNSEndpoint.

External-DNS should not create DNS records for Ingress that don't have a loadBalancer status