You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We use external-dns to sync records to AWS Route 53 and we are running into some of the AWS limits. At the moment we have a headless service with external-dns annotation to create main A record. However, we've also noticed that external-dns creates record per each pod which creates records that we don't need, but also they contribute to some of the AWS limits. The problem only got worse once we started horizontally scale those pods :)
FWIU currently there is no flag or option to make that behavior optional, so I wanted to ask it that's the case then would opening a ticket make sense here. We'd also be happy to code contribute if required.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
Hi There,
We use external-dns to sync records to AWS Route 53 and we are running into some of the AWS limits. At the moment we have a headless service with
external-dnsannotation to create main A record. However, we've also noticed thatexternal-dnscreates record per each pod which creates records that we don't need, but also they contribute to some of the AWS limits. The problem only got worse once we started horizontally scale those pods :)FWIU currently there is no flag or option to make that behavior optional, so I wanted to ask it that's the case then would opening a ticket make sense here. We'd also be happy to code contribute if required.
Beta Was this translation helpful? Give feedback.
All reactions