External-dns: Do not wait forever when API server is unreachable

Created on 31 Jul 2017 · 16Comments · Source: kubernetes-sigs/external-dns

Currently it tries forever to connect to api server.

Should be:

Have a backoff and max wait time before failing
Have a health check that indicates that ExternalDNS is functioning, e.g.
- Can speak to the API server
- checks on dns provider availability
- ...

kinfeature lifecyclrotten sizM

Source

linki

👍8

Most helpful comment

Would be great to have backoffs on AWS when throttling is occurring.

{"level":"error","msg":"Throttling: Rate exceeded\n\tstatus code: 400, request id: c8b2c3e2-8f25-11e7-b1f4-1fad538d0a89","time":"2017-09-01T14:56:51Z"}

sstarcher on 1 Sep 2017

👍6

All 16 comments

Health check should include checks on dns provider availability

ideahitme on 16 Aug 2017

👍1

@ideahitme added it to the desription.

linki on 16 Aug 2017

Would be great to have backoffs on AWS when throttling is occurring.

{"level":"error","msg":"Throttling: Rate exceeded\n\tstatus code: 400, request id: c8b2c3e2-8f25-11e7-b1f4-1fad538d0a89","time":"2017-09-01T14:56:51Z"}

sstarcher on 1 Sep 2017

👍6

I'm having this issue two with two k8s clusters both running external-dns in the same AWS account.

tsuna on 5 Feb 2019

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

fejta-bot on 7 May 2019

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten

fejta-bot on 6 Jun 2019

/remove-lifecycle rotten

tsuna on 6 Jun 2019

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

fejta-bot on 4 Sep 2019

/remove-lifecycle stale

Raffo on 4 Sep 2019

This would actually help a soft dependency problem we have when provisioning new clusters. Using Weave Flux, we deploy both kube2iam and external-dns, and if external-dns comes up before kube2iam, external-dns won't have permission to talk to AWS. There is nothing except human intervention that will get us out of this error state. If /healthz would return something other than 200 when calls to the provider are failing, the cluster could restart the pod and let it come up with proper IAM creds (in our use case)

acobaugh on 15 Oct 2019

👍5

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

fejta-bot on 13 Jan 2020

/remove-lifecycle stale

linki on 14 Jan 2020

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

fejta-bot on 13 Apr 2020

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten

fejta-bot on 13 May 2020

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

fejta-bot on 12 Jun 2020

@fejta-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

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.