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 have a number of EKS clusters, each with multiple external-dns deployments.
These deployments have been running successfully for some period using the default TXT registry.
We are in the process of moving over to the DynamoDB registry. Testing was successful on deployments with a small number of zones and small set of records.
When migrating a deployment with 10 zones, and about 300 records, external-dns started crashing with a panic:
What happened:
We have a number of EKS clusters, each with multiple external-dns deployments.
These deployments have been running successfully for some period using the default TXT registry.
We are in the process of moving over to the DynamoDB registry. Testing was successful on deployments with a small number of zones and small set of records.
When migrating a deployment with 10 zones, and about 300 records, external-dns started crashing with a panic:
This appears to crash on the first batch, as nothing has yet been written to DynamoDB, even after multiple panics.
What you expected to happen:
Should not panic.
How to reproduce it (as minimally and precisely as possible):
Have an existing external-dns deployment configured, with more than 25 records (the DynamoDB Batch size is 25)
Anything else we need to know?:
Environment: EKS Nodes on EC2
external-dns --version
): imageregistry.k8s.io/external-dns/external-dns:v0.14.0
1.14.3
The text was updated successfully, but these errors were encountered: