Rolling update of controller pods caused recreation of external-dns records

[max-rocket-internet]

What keywords did you search in NGINX Ingress controller issues before filing this one? (If you have found any duplicates, you should instead reply there.): update-status, external-dns

Is this a BUG REPORT or FEATURE REQUEST? (choose one): BUG REPORT

NGINX Ingress controller version: 0.25.1

Kubernetes version (use kubectl version): v1.13

Environment:

• Cloud provider or hardware configuration: AWS EKS
• OS (e.g. from /etc/os-release): EKS AMI
• Install tools: Helm Chart version 1.17.1

What happened:

Started rolling update of controllers to adjust pod resources and external-dns delete and recreated all DNS records.

Related issue here: kubernetes-sigs/external-dns#1289

We set publishService as we want external-dns to use the ELB from the ingress-controller service for the DNS records:

controller:
  publishService:
    enabled: true
    pathOverride: default/ingress01-nginx-ingress-controller

It was metioned that this might be related to the update-status-on-shutdown option. But we've used both extern-dns and nginx-ingress for a long time and never seen anything like this. Updated the charts dozens of times without any issues

What you expected to happen:

No external-dns changes.

How to reproduce it (as minimally and precisely as possible):

I'm not sure.

Can anyone advise what in nginx-ingress might cause this?

[max-rocket-internet]

It appears my searching wasn't good enough. My issue here is covered in:

• Update documentation to call out --update-status-on-shutdown for external DNS #1877
• External DNS deleted all Route53 records on cluster rolling update kubernetes-sigs/external-dns#414

[max-rocket-internet]

I will set --update-status-on-shutdown=false

[jetersen]

For those stumbling into this issue here is the helm chart value needed:

controller:
  extraArgs:
    update-status-on-shutdown: "false"