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

Oracle DNS: ExternalDNS may hit API Rate limit #3994

Closed
anders-swanson opened this issue Oct 18, 2023 · 1 comment · Fixed by #4049
Closed

Oracle DNS: ExternalDNS may hit API Rate limit #3994

anders-swanson opened this issue Oct 18, 2023 · 1 comment · Fixed by #4049
Labels
kind/bug Categorizes issue or PR as related to a bug.

Comments

@anders-swanson
Copy link
Contributor

What happened:

When using Oracle provider, ExternalDNS may hit the OCI DNS rate limit, especially if multiple clusters in the same tenancy are using ExternalDNS, or if you manage a large amount of records.

When the rate limit is consistently hit, users experience a delay in DNS propagation.

What you expected to happen:

ExternalDNS works seamlessly without errors creating/listing records.

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

  1. Install ExternalDNS using the oracle provider on multiple clusters (5+).
  2. Create several records (10+) on each cluster using ExternalDNS.
  3. See rate limiting errors and delays in DNS propagation.

Anything else we need to know?:

Some providers, e.g., AWs, implement DNS zone caching. A similar implementation in the Oracle provider will help with rate limiting by reducing the amount of outbound calls.

Environment:

  • External-DNS version (use external-dns --version): v0.13.1
  • DNS provider: oracle
  • Others:
@anders-swanson anders-swanson added the kind/bug Categorizes issue or PR as related to a bug. label Oct 18, 2023
@anders-swanson
Copy link
Contributor Author

I am happy to work on this issue.

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

Successfully merging a pull request may close this issue.

1 participant