Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Missing events with enabled --events #4086

Closed
nefelim4ag opened this issue Dec 1, 2023 · 1 comment
Closed

Missing events with enabled --events #4086

nefelim4ag opened this issue Dec 1, 2023 · 1 comment
Labels
kind/bug Categorizes issue or PR as related to a bug.

Comments

@nefelim4ag
Copy link
Contributor

nefelim4ag commented Dec 1, 2023

What happened:
External-dns running on a EKS cluster with --events. This particular one with Godaddy controller.
After one hour if I remove one of the ingress-nginx and trigger an update of the ingress load balancer status.
External-dns just do nothing.

On upgrade that leads to complete replacement of all IP Addresses in LoadBalancer status and old addresses in DNS.

What you expected to happen:
External DNS receive the event and processes it.

How to reproduce it (as minimally and precisely as possible):
Run external-dns with --events and trigger load balancer status updates in some way.

I'm working on reproducing and searching for the root cause.

Anything else we need to know?:
Possibly caused by the disabled resync period here:
https://github.com/kubernetes-sigs/external-dns/blob/master/source/ingress.go#L94
AFAIK watch operations in K8S were always broken in some way, for different reasons.
Default controller implementation, define it to 10h according to:
https://github.com/kubernetes-sigs/controller-runtime/blob/a50d5d7a49753b006d783684d7e1c7d6884ca462/pkg/cache/cache.go#L146C1-L151C72

Environment:

  • External-DNS version: 1.14.0 (build from the master, I'm depending on some merged, but not yet released patches)
  • DNS provider: GoDaddy
@nefelim4ag nefelim4ag added the kind/bug Categorizes issue or PR as related to a bug. label Dec 1, 2023
@nefelim4ag
Copy link
Contributor Author

nefelim4ag commented Dec 2, 2023

Closed, for now, looks like the source of the problem is different

For history, the root cause: #4087

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Categorizes issue or PR as related to a bug.
Projects
None yet
Development

No branches or pull requests

1 participant