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.

Sign up for GitHub

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

Jump to bottom

Synchronize DNS reconciliation when scaling a headless Service #4113

Closed
github-amine-kherbouche opened this issue Dec 15, 2023 · 8 comments · May be fixed by #4427
Closed

Synchronize DNS reconciliation when scaling a headless Service #4113

github-amine-kherbouche opened this issue Dec 15, 2023 · 8 comments · May be fixed by #4427
Labels
kind/feature Categorizes issue or PR as related to a new feature. lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed.

Comments

@github-amine-kherbouche
Copy link

What would you like to be added:

A watch mechanism for Headless services' Endpoint updates, ensuring automatic reconciliation of DNS records when scaling operations occur. This enhancement intends to maintain synchronization between the service's DNS entries and the underlying endpoints when scaling the Headless service.

Why is this needed:

Currently, External-DNS generates DNS records upon the creation of a headless Service. However, when scaling deployment/statefulset, updates to the Endpoint resource containing new list of IP addresses don't trigger External-DNS updates. This omission occurs due to the lack of Endpoint event monitoring.

The existing workarounds involve either:

Manually triggering the Service resource update with an annotation.
Utilizing a small --interval in External-DNS to enforce recurrent updates. However, this approach has drawbacks:

  • Asynchronous updates
  • Quick rate limiting by the DNS provider API (such as Route53) due to the number of External-DNS instances.

Consequently, implementing Endpoint event monitoring would streamline the synchronization between scaling operations and DNS updates for Headless services, mitigating the need for manual interventions and/or lowering the update interval
@github-amine-kherbouche github-amine-kherbouche added the kind/feature Categorizes issue or PR as related to a new feature. label Dec 15, 2023
@k8s-triage-robot
Copy link

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Mark this issue as fresh with /remove-lifecycle stale
  • Close this issue with /close
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Mar 14, 2024
@k8s-triage-robot
Copy link

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Mark this issue as fresh with /remove-lifecycle rotten
  • Close this issue with /close
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

@k8s-ci-robot k8s-ci-robot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Apr 13, 2024
@IliaGe
Copy link

IliaGe commented Apr 16, 2024

We got the same issue, External-DNS is very very slow in terms of updating a headless Service object

@or-he-MA
Copy link

Also experiencing the same issue. Currently external-dns takes about ~5 min to update records.

@bakavets-ma
Copy link

Hey! We have this issue as well.

@mikeh096
Copy link

this would be a great feature, lowering update interval really isn't good enough

@tufitko tufitko mentioned this issue May 1, 2024
Open
2 tasks
@k8s-triage-robot
Copy link

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Reopen this issue with /reopen
  • Mark this issue as fresh with /remove-lifecycle rotten
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close not-planned

@k8s-ci-robot k8s-ci-robot closed this as not planned Won't fix, can't repro, duplicate, stale May 17, 2024
@k8s-ci-robot
Copy link
Contributor

@k8s-triage-robot: Closing this issue, marking it as "Not Planned".

In response to this:

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Reopen this issue with /reopen
  • Mark this issue as fresh with /remove-lifecycle rotten
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close not-planned

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-sigs/prow repository.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
kind/feature Categorizes issue or PR as related to a new feature. lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed.
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

feat(source/service): watch headless endpoints tufitko/external-dns
7 participants
@k8s-ci-robot @k8s-triage-robot @or-he-MA @IliaGe @github-amine-kherbouche @mikeh096 @bakavets-ma