external-dns icon indicating copy to clipboard operation
external-dns copied to clipboard

Published 20 hours ago • verified publisher icon kubernetes-sigs

support multiple replicas for reliability

Open bkk-bcd opened this issue 3 years ago • 26 comments

What would you like to be added: Multiple replicas for reliability, similar to how https://github.com/kubernetes-sigs/aws-load-balancer-controller works using leader election.

Why is this needed: Improve reliability.

bkk-bcd avatar Nov 11 '21 13:11 bkk-bcd

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:

  • 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 or PR as fresh with /remove-lifecycle stale
  • Mark this issue or PR as rotten with /lifecycle rotten
  • Close this issue or PR with /close
  • Offer to help out with Issue Triage

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

/lifecycle stale

k8s-triage-robot avatar Feb 09 '22 13:02 k8s-triage-robot

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:

  • 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 or PR as fresh with /remove-lifecycle rotten
  • Close this issue or PR with /close
  • Offer to help out with Issue Triage

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

/lifecycle rotten

k8s-triage-robot avatar Mar 11 '22 13:03 k8s-triage-robot

/remove-lifecycle rotten

Legion2 avatar Mar 11 '22 13:03 Legion2

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:

  • 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 or PR as fresh with /remove-lifecycle stale
  • Mark this issue or PR as rotten with /lifecycle rotten
  • Close this issue or PR with /close
  • Offer to help out with Issue Triage

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

/lifecycle stale

k8s-triage-robot avatar Jun 09 '22 14:06 k8s-triage-robot

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:

  • 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 or PR as fresh with /remove-lifecycle rotten
  • Close this issue or PR with /close
  • Offer to help out with Issue Triage

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

/lifecycle rotten

k8s-triage-robot avatar Jul 09 '22 14:07 k8s-triage-robot

/remove-lifecycle rotten

bkk-bcd avatar Jul 09 '22 18:07 bkk-bcd

xref:

  • #164

mkilchhofer avatar Aug 03 '22 12:08 mkilchhofer

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:

  • 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 or PR as fresh with /remove-lifecycle stale
  • Mark this issue or PR as rotten with /lifecycle rotten
  • Close this issue or PR with /close
  • Offer to help out with Issue Triage

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

/lifecycle stale

k8s-triage-robot avatar Nov 01 '22 12:11 k8s-triage-robot

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:

  • 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 or PR as fresh with /remove-lifecycle rotten
  • Close this issue or PR with /close
  • Offer to help out with Issue Triage

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

/lifecycle rotten

k8s-triage-robot avatar Dec 01 '22 13:12 k8s-triage-robot

For what use-case is it a problem if DNS records occasionally cannot be updated for a minute?

benjimin avatar Dec 04 '22 10:12 benjimin

For what use-case is it a problem if DNS records occasionally cannot be updated for a minute?

I'd say almost any cluster-level "addon" to Kubernetes supports this and it's good practice to do so. Other SIGS projects (I use) supporting HA:

  • https://github.com/kubernetes-sigs/aws-load-balancer-controller/
  • https://github.com/kubernetes/autoscaler
  • https://github.com/kubernetes-sigs/aws-ebs-csi-driver
  • https://github.com/kubernetes-sigs/aws-efs-csi-driver

Use cases are all related to minimization of downtime:

  • Minimize downtime if Pod gets terminated and image cannot be pulled again due to Registry/PullSecret issues
  • Minimize downtime on node patching/replacing since there is a ready replica pod running on a 2nd node already which can take over in seconds (configurable leader election interval)
  • Rolling update and ensure that the new instance does not do something until the "old" one is correctly stopped
  • workaround issues with cluster-autoscaler (not working anymore or already scaled out to max configured) in case of a node failure and a full cluster

I know, some of the points can be addressed differently (eg. PriorityClass).

mkilchhofer avatar Dec 04 '22 19:12 mkilchhofer

/remove-lifecycle rotten

+1 to this feature.

fp-big5 avatar Dec 27 '22 14:12 fp-big5

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-triage-robot avatar Mar 27 '23 14:03 k8s-triage-robot

Not stale

mkilchhofer avatar Mar 27 '23 22:03 mkilchhofer

/remove-lifecycle stale

felipewnp avatar Mar 30 '23 18:03 felipewnp

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-triage-robot avatar Jun 28 '23 19:06 k8s-triage-robot

/remove-lifecycle stale

Constantin07 avatar Jun 28 '23 20:06 Constantin07

/remove-lifecycle stale

On Wed, Jun 28, 2023, 16:27 Kubernetes Triage Robot < @.***> wrote:

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:

Please send feedback to sig-contributor-experience at kubernetes/community https://github.com/kubernetes/community.

/lifecycle stale

— Reply to this email directly, view it on GitHub https://github.com/kubernetes-sigs/external-dns/issues/2430#issuecomment-1611979843, or unsubscribe https://github.com/notifications/unsubscribe-auth/AIEQPKSV2I5XHOLC37V4AF3XNSASHANCNFSM5H2N7QOQ . You are receiving this because you commented.Message ID: @.***>

felipewnp avatar Jun 28 '23 21:06 felipewnp

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-triage-robot avatar Jan 23 '24 13:01 k8s-triage-robot

/remove-lifecycle stale

kstevensonnv avatar Jan 23 '24 13:01 kstevensonnv

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-triage-robot avatar Apr 22 '24 14:04 k8s-triage-robot

/remove-lifecycle stale

kstevensonnv avatar Apr 22 '24 14:04 kstevensonnv