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

support multiple replicas for reliability #2430

Open
bkk-bcd opened this issue Nov 11, 2021 · 26 comments
Open

support multiple replicas for reliability #2430

bkk-bcd opened this issue Nov 11, 2021 · 26 comments
Labels
kind/feature Categorizes issue or PR as related to a new feature.

Comments

@bkk-bcd
Copy link

bkk-bcd commented Nov 11, 2021 •
edited
Loading

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 bkk-bcd added the kind/feature Categorizes issue or PR as related to a new feature. label Nov 11, 2021
@k8s-triage-robot
Copy link

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-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 Feb 9, 2022
@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 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-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 Mar 11, 2022
@Legion2
Copy link

Legion2 commented Mar 11, 2022

/remove-lifecycle rotten

@k8s-ci-robot 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 mac-chaffee mentioned this issue May 26, 2022
Merged
1 task
@k8s-triage-robot
Copy link

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-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 Jun 9, 2022
@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 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-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 Jul 9, 2022
@bkk-bcd
Copy link
Author

bkk-bcd commented Jul 9, 2022

/remove-lifecycle rotten

@k8s-ci-robot 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
@mkilchhofer
Copy link

mkilchhofer commented Aug 3, 2022 •
edited
Loading

xref:

@k8s-triage-robot
Copy link

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-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 Nov 1, 2022
@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 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-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 Dec 1, 2022
@benjimin
Copy link

benjimin commented Dec 4, 2022

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

@mkilchhofer
Copy link

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

@alebedev87 alebedev87 mentioned this issue Dec 12, 2022
Merged
@fp-big5
Copy link

fp-big5 commented Dec 27, 2022 •
edited
Loading

/remove-lifecycle rotten

+1 to this feature.

@k8s-ci-robot 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-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 27, 2023
@stevehipwell stevehipwell mentioned this issue Mar 27, 2023
Closed
2 tasks
@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 Jun 28, 2023
@Constantin07
Copy link

/remove-lifecycle stale

@k8s-ci-robot 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
@felipewnp
Copy link

felipewnp commented Jun 28, 2023 via email

@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 Jan 23, 2024
@kstevensonnv
Copy link

/remove-lifecycle stale

@k8s-ci-robot 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 added a commit to alphagov/govuk-helm-charts that referenced this issue Apr 10, 2024
@nimalank7
Use official Kubernetes external-dns chart instead of Bitnami
613304c 
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
nimalank7 added a commit to alphagov/govuk-helm-charts that referenced this issue Apr 10, 2024
@nimalank7
Use official Kubernetes external-dns chart instead of Bitnami
a666c37 
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
nimalank7 added a commit to alphagov/govuk-helm-charts that referenced this issue Apr 11, 2024
@nimalank7
Use official Kubernetes external-dns chart instead of Bitnami
09b0cc5 
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
@nimalank7 nimalank7 mentioned this issue Apr 11, 2024
Merged
nimalank7 added a commit to alphagov/govuk-helm-charts that referenced this issue Apr 11, 2024
@nimalank7
Use official Kubernetes external-dns chart instead of Bitnami
ca96c36 
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
nimalank7 added a commit to alphagov/govuk-helm-charts that referenced this issue Apr 11, 2024
@nimalank7
Use official Kubernetes external-dns chart instead of Bitnami
d445927 
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
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 Apr 22, 2024
@kstevensonnv
Copy link

/remove-lifecycle stale

@k8s-ci-robot 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 mzeeshan1 mentioned this issue Jun 4, 2024
Closed
@migruiz4 migruiz4 mentioned this issue Jun 5, 2024
Merged
4 tasks
@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 Jul 21, 2024
@felipewnp
Copy link

/remove-lifecycle stale

@k8s-ci-robot 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 Azahorscak mentioned this issue Aug 2, 2024
Closed
@ivankatliarchuk ivankatliarchuk mentioned this issue Oct 3, 2024
Open
2 tasks
@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 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
@felipewnp
Copy link

/remove-lifecycle stale

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.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
10 participants
@mkilchhofer @Constantin07 @Legion2 @benjimin @k8s-ci-robot @felipewnp @kstevensonnv @k8s-triage-robot @bkk-bcd @fp-big5