janz0390

We are seeing the exact same issue with Route53 after attempting to upgrade to 0.12.0. We are upgrading from v0.5.14 in the same cluster where this issue did not exist...

Adding debug logs: ``` time="2022-07-20T19:59:38Z" level=debug msg="Endpoints generated from ingress: 00a8982b-3a6d-4f87-b603-5f25090a2c01/foo-qt-primary-rpc: [00a8982b-3a6d-4f87-b603-5f25090a2c01.foo.bar.net 0 IN CNAME REDACTED.elb.us-east-2.amazonaws.com [] primary.00a8982b-3a6d-4f87-b603-5f25090a2c01.foo.bar.net 0 IN CNAME REDACTED.elb.us-east-2.amazonaws.com [] 00a8982b-3a6d-4f87-b603-5f25090a2c01.foo.bar.net 0 IN CNAME REDACTED.elb.us-east-2.amazonaws.com [] primary.00a8982b-3a6d-4f87-b603-5f25090a2c01.foo.bar.net...