support multiple replicas for reliability #2430

bkk-bcd · 2021-11-11T13:13:39Z

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.

k8s-triage-robot · 2022-02-09T13:41:23Z

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 · 2022-03-11T13:43:58Z

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

Legion2 · 2022-03-11T13:52:08Z

/remove-lifecycle rotten

k8s-triage-robot · 2022-06-09T14:22:56Z

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 · 2022-07-09T14:48:59Z

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

bkk-bcd · 2022-07-09T18:27:34Z

/remove-lifecycle rotten

mkilchhofer · 2022-08-03T12:24:48Z

xref:

Support running multiple instances of external-dns with leader election #164

k8s-triage-robot · 2022-11-01T12:54:06Z

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 · 2022-12-01T13:23:17Z

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

benjimin · 2022-12-04T10:42:19Z

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

mkilchhofer · 2022-12-04T19:57:02Z

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:

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).

fp-big5 · 2022-12-27T14:14:49Z

/remove-lifecycle rotten

+1 to this feature.

k8s-triage-robot · 2023-03-27T14:23:53Z

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

Constantin07 · 2023-06-28T20:04:36Z

/remove-lifecycle stale

felipewnp · 2023-06-28T21:51:49Z

/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: - Mark this issue as fresh with /remove-lifecycle stale - Close this issue with /close - Offer to help out with Issue Triage <https://www.kubernetes.dev/docs/guide/issue-triage/> 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 <#2430 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AIEQPKSV2I5XHOLC37V4AF3XNSASHANCNFSM5H2N7QOQ> . You are receiving this because you commented.Message ID: ***@***.***>

k8s-triage-robot · 2024-01-23T13:46:59Z

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

kstevensonnv · 2024-01-23T13:47:57Z

/remove-lifecycle stale

Description: - Official Kubernetes external-dns chart is located [here](https://github.com/kubernetes-sigs/external-dns/tree/master/charts/external-dns) - Previously in production we were running 3 but the bitnami chart doesn’t have any leader selection so all external-dnspods were running thinking they were the only one. Kubernetes external-dns doesn’t support multiple replicas so removing this entirely. See the discussion [here](kubernetes-sigs/external-dns#2430) - PR closes #1744

k8s-triage-robot · 2024-04-22T14:28:14Z

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

kstevensonnv · 2024-04-22T14:49:08Z

/remove-lifecycle stale

k8s-triage-robot · 2024-07-21T15:29:48Z

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

felipewnp · 2024-07-21T19:57:54Z

/remove-lifecycle stale

k8s-triage-robot · 2024-10-19T20:28:53Z

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

felipewnp · 2024-10-20T01:27:17Z

/remove-lifecycle stale

bkk-bcd added the kind/feature Categorizes issue or PR as related to a new feature. label Nov 11, 2021

k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Feb 9, 2022

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 Mar 11, 2022

k8s-ci-robot removed the lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. label Mar 11, 2022

mac-chaffee mentioned this issue May 26, 2022

Changed the Deployment strategy to 'Recreate' so multiple external-dns pods don't conflict with each other. #2772

Merged

1 task

k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jun 9, 2022

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 Jul 9, 2022

k8s-ci-robot removed the lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. label Jul 9, 2022

k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Nov 1, 2022

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 Dec 1, 2022

alebedev87 mentioned this issue Dec 12, 2022

OCPBUGS-3630: deployment: enforce recreate strategy to avoid conflicts during upgrades openshift/external-dns-operator#185

Merged

k8s-ci-robot removed the lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. label Dec 27, 2022

k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Mar 27, 2023

stevehipwell mentioned this issue Mar 27, 2023

allow change replicas #3487

Closed

2 tasks

k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jun 28, 2023

k8s-ci-robot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jun 28, 2023

k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jan 23, 2024

k8s-ci-robot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jan 23, 2024

nimalank7 mentioned this issue Apr 11, 2024

Use official Kubernetes external-dns chart instead of Bitnami alphagov/govuk-helm-charts#1951

Merged

k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Apr 22, 2024

k8s-ci-robot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Apr 22, 2024

mzeeshan1 mentioned this issue Jun 4, 2024

[bitnami/external-dns] Why bitnami chart allows to modify number of replicas for external dns when external dns does not support multiple replicas bitnami/charts#26682

Closed

migruiz4 mentioned this issue Jun 5, 2024

[bitnami/external-dns] Major release: drop support for multiple replicas and DaemonSet bitnami/charts#26759

Merged

4 tasks

k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jul 21, 2024

k8s-ci-robot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jul 21, 2024

Azahorscak mentioned this issue Aug 2, 2024

External-dns replicas option removed in chart v8.x bitnami/charts#28638

Closed

ivankatliarchuk mentioned this issue Oct 3, 2024

Allow replica count to be set to zero #4784

Open

2 tasks

k8s-ci-robot added lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Oct 19, 2024

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

support multiple replicas for reliability #2430

support multiple replicas for reliability #2430

bkk-bcd commented Nov 11, 2021 •

edited

Loading

k8s-triage-robot commented Feb 9, 2022

k8s-triage-robot commented Mar 11, 2022

Legion2 commented Mar 11, 2022

k8s-triage-robot commented Jun 9, 2022

k8s-triage-robot commented Jul 9, 2022

bkk-bcd commented Jul 9, 2022

mkilchhofer commented Aug 3, 2022 •

edited

Loading

k8s-triage-robot commented Nov 1, 2022

k8s-triage-robot commented Dec 1, 2022

benjimin commented Dec 4, 2022

mkilchhofer commented Dec 4, 2022

fp-big5 commented Dec 27, 2022 •

edited

Loading

k8s-triage-robot commented Mar 27, 2023

Constantin07 commented Jun 28, 2023

felipewnp commented Jun 28, 2023 via email

k8s-triage-robot commented Jan 23, 2024

kstevensonnv commented Jan 23, 2024

k8s-triage-robot commented Apr 22, 2024

kstevensonnv commented Apr 22, 2024

k8s-triage-robot commented Jul 21, 2024

felipewnp commented Jul 21, 2024

k8s-triage-robot commented Oct 19, 2024

felipewnp commented Oct 20, 2024

support multiple replicas for reliability #2430

support multiple replicas for reliability #2430

Comments

bkk-bcd commented Nov 11, 2021 • edited Loading

k8s-triage-robot commented Feb 9, 2022

k8s-triage-robot commented Mar 11, 2022

Legion2 commented Mar 11, 2022

k8s-triage-robot commented Jun 9, 2022

k8s-triage-robot commented Jul 9, 2022

bkk-bcd commented Jul 9, 2022

mkilchhofer commented Aug 3, 2022 • edited Loading

k8s-triage-robot commented Nov 1, 2022

k8s-triage-robot commented Dec 1, 2022

benjimin commented Dec 4, 2022

mkilchhofer commented Dec 4, 2022

fp-big5 commented Dec 27, 2022 • edited Loading

k8s-triage-robot commented Mar 27, 2023

Constantin07 commented Jun 28, 2023

felipewnp commented Jun 28, 2023 via email

k8s-triage-robot commented Jan 23, 2024

kstevensonnv commented Jan 23, 2024

k8s-triage-robot commented Apr 22, 2024

kstevensonnv commented Apr 22, 2024

k8s-triage-robot commented Jul 21, 2024

felipewnp commented Jul 21, 2024

k8s-triage-robot commented Oct 19, 2024

felipewnp commented Oct 20, 2024

bkk-bcd commented Nov 11, 2021 •

edited

Loading

mkilchhofer commented Aug 3, 2022 •

edited

Loading

fp-big5 commented Dec 27, 2022 •

edited

Loading