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.

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

sig-cl/kubeadm: Use etcd's learner mode #3614

Open
8 tasks done
neolit123 opened this issue Oct 12, 2022 · 11 comments
Open
8 tasks done

sig-cl/kubeadm: Use etcd's learner mode #3614

neolit123 opened this issue Oct 12, 2022 · 11 comments
Labels
sig/cluster-lifecycle Categorizes an issue or PR as relevant to SIG Cluster Lifecycle.

Comments

@neolit123
Copy link
Member

neolit123 commented Oct 12, 2022

Enhancement Description

Please keep this description up to date. This will help the Enhancement Team to track the evolution of the enhancement efficiently.

@neolit123 neolit123 added the sig/cluster-lifecycle Categorizes an issue or PR as relevant to SIG Cluster Lifecycle. label Oct 12, 2022
@neolit123 neolit123 changed the title sig-cluster-lifecycle/kubeadm: etcd learner mode sig-cluster-lifecycle/kubeadm: Use etcd's learner mode Oct 12, 2022
@neolit123 neolit123 changed the title sig-cluster-lifecycle/kubeadm: Use etcd's learner mode sig-cl/kubeadm: Use etcd's learner mode Oct 12, 2022
@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 Jan 10, 2023
@neolit123 neolit123 removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jan 12, 2023
@pacoxu
Copy link
Member

pacoxu commented Jan 31, 2023

The alpha implemented PR was merged: kubernetes/kubernetes#113318.

E2E test will be added by kubernetes/kubeadm#2807 and kubernetes/test-infra#28574.

I think this will be alpha in v1.27. The KEP was merged in v1.26 release cycle #3615.
A KEP update is needed. I will submit a PR ASAP.

We plan to move this to alpha in v1.27.

@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 May 8, 2023
@neolit123 neolit123 removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label May 8, 2023
@pacoxu

This comment was marked as resolved.

@pacoxu
Copy link
Member

pacoxu commented May 9, 2023

I prefer to wait for more feedback in v1.28 release cycle and promote it to beta in a later release(1.29 or later).

@neolit123
Copy link
Member Author

I prefer to wait for more feedback in v1.28 release cycle and promote it to beta in a later release(1.29 or later).

SGTM

@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 28, 2024
@pacoxu
Copy link
Member

pacoxu commented Jan 28, 2024

/remove-lifecycle stale
needs more feedback

Is there any known issue about this feature?

@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 28, 2024
@neolit123
Copy link
Member Author

Is there any known issue about this feature?

we can aim for GA in 1.30 unless any blocking issue appears.

@pacoxu
Copy link
Member

pacoxu commented Jan 29, 2024

Is there any known issue about this feature?

we can aim for GA in 1.30 unless any blocking issue appears.

I prefer we may wait for at least another 1 or 2 release cycles for feedbacks to make this GA, as most users are not using v1.29 yet, which make it beta, by default enabled.

@neolit123
Copy link
Member Author

I prefer we may wait for at least another 1 or 2 release cycles for feedbacks to make this GA, as most users are not using v1.29 yet, which make it beta, by default enabled.

SGTM.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
sig/cluster-lifecycle Categorizes an issue or PR as relevant to SIG Cluster Lifecycle.
Projects
None yet
Development

No branches or pull requests

4 participants