Ignore the custom ProviderSpecific in aws provider

[iamLunie]

I created a custom provider for my cf zero trust that relies on the dns created in route53

The setup is, i have two providers deployed in a cluster:

• aws provider
• custom provider

# ingress.yml
apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
  name: public-ingress
  annotations:
    external-dns.alpha.kubernetes.io/webhook: apple
spec:
  rules:
  - host: a.service.com
    http:
      paths:
      - backend:
          service:
            name: service
            port:
              name: http
        path: /
        pathType: ImplementationSpecific

The first povider (aws) creates a.service.com (no issues)
The second provider(custom) relies on external-dns.alpha.kubernetes.io/webhook: apple settings.

The logic seems to be working as expected. However, the aws provider is detecting these custom annotations as new, so they don’t match the existing records, this keeps the aws provider to update the records, even though there is no update.

Is there a way to ignore the custom provider annotations?

[iamLunie]

Nevermind , i adjusted my provider to avoid using that specificProvider property. still, it would be nice if it were ignored by default unless its explicitly part of the setup..