-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
Hetzner causing rate limit error and not handling it correctly #2569
Comments
Workaround: Edit: /run/systemd/resolve/resolv.conf |
Please note that we removed the Hetzner provider due to a DOS attack from the library provider. See #2660 for future follow ups. |
The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs. This bot triages issues and PRs according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs. This bot triages issues and PRs according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle rotten |
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs. This bot triages issues and PRs according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /close |
@k8s-triage-robot: Closing this issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
What happened:
Hetzner not creating records due to rate limit error, and not handle it correctly (ie: slowing down).
What you expected to happen:
to detect rate limit and slow down, although the detection should be handled by: https://git.blindage.org/21h/hcloud-dns/src/commit/d31cdce4149f7248e6d08adec2ca5a81ff150ce5/zones.go#L92 which doesn't check the response status code and unmarshales to the wrong type, creating the illusion of no error.
Use CreateRecordBulk and UpdateRecordBulk to avoid reaching the limit at the first place.
How to reproduce it (as minimally and precisely as possible):
just use hetzner with a cluster with many ingresses.
Environment:
external-dns --version
): 1.7.1The text was updated successfully, but these errors were encountered: