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

Ability to create dynamic HA clusters with kubeadm #357

Closed
luxas opened this issue Jul 26, 2017 · 77 comments · Fixed by #3150
Closed

Ability to create dynamic HA clusters with kubeadm #357

luxas opened this issue Jul 26, 2017 · 77 comments · Fixed by #3150
Assignees
Labels
kind/feature Categorizes issue or PR as related to a new feature. sig/cluster-lifecycle Categorizes an issue or PR as relevant to SIG Cluster Lifecycle. stage/stable Denotes an issue tracking an enhancement targeted for Stable/GA status tracked/no Denotes an enhancement issue is NOT actively being tracked by the Release Team

Comments

@luxas
Copy link
Member

luxas commented Jul 26, 2017

Feature Description


Edit by @spiffxp:

Per #357 (comment) we should consider kicking this out of of v1.14 and using a separate tracking issue for the actual KEP being implemented this cycle: 20190122-Certificates-copy-for-kubeadm-join--control-plane.md

@k8s-ci-robot k8s-ci-robot added sig/cluster-lifecycle Categorizes an issue or PR as relevant to SIG Cluster Lifecycle. kind/feature Categorizes issue or PR as related to a new feature. labels Jul 26, 2017
@luxas luxas added stage/alpha Denotes an issue tracking an enhancement targeted for Alpha status and removed kind/feature Categorizes issue or PR as related to a new feature. labels Jul 26, 2017
@luxas luxas added this to the 1.8 milestone Jul 26, 2017
@luxas
Copy link
Member Author

luxas commented Jul 26, 2017

Hoping to get an alpha implementation of this in v1.8. Might or might not work out. At least a ready design doc should be ready at the end of the v1.8 cycle.

@luxas luxas modified the milestones: next-milestone, 1.8 Aug 14, 2017
@luxas
Copy link
Member Author

luxas commented Aug 15, 2017

@kubernetes/sig-cluster-lifecycle-feature-requests I moved this to next-milestone as no code for this is shipping in v1.8, only design

@luxas
Copy link
Member Author

luxas commented Oct 27, 2017

Targeting alpha in v1.9

@luxas luxas modified the milestones: next-milestone, 1.9 Oct 27, 2017
@luxas luxas mentioned this issue Oct 27, 2017
22 tasks
@zacharysarah
Copy link
Contributor

@luxas 👋 Please indicate in the 1.9 feature tracking board
whether this feature needs documentation. If yes, please open a PR and add a link to the tracking spreadsheet. Thanks in advance!

@luxas
Copy link
Member Author

luxas commented Nov 24, 2017

This feature didn't make it into v1.9

@luxas luxas modified the milestones: v1.9, next-milestone Nov 24, 2017
@idvoretskyi
Copy link
Member

@luxas @kubernetes/sig-cluster-lifecycle-feature-requests still on track for 1.10?

@k8s-ci-robot k8s-ci-robot added the kind/feature Categorizes issue or PR as related to a new feature. label Jan 15, 2018
@roberthbailey
Copy link
Contributor

This has been de-prioritized for 1.10 in favor of trying to get the existing kubeadm functionality promoted from beta to GA.

@idvoretskyi
Copy link
Member

@roberthbailey thanks

@justaugustus
Copy link
Member

@luxas / @timothysc -- Any plans for this in 1.11?

If so, can you please ensure the feature is up-to-date with the appropriate:

  • Description
  • Milestone
  • Assignee(s)
  • Labels:
    • stage/{alpha,beta,stable}
    • sig/*
    • kind/feature

cc @idvoretskyi

@luxas
Copy link
Member Author

luxas commented May 11, 2018

@justaugustus No plans to move feature state this release, incremental improvements.

/lifecycle frozen

@k8s-ci-robot k8s-ci-robot added the lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. label May 11, 2018
@justaugustus
Copy link
Member

/remove-lifecycle frozen

@k8s-ci-robot k8s-ci-robot removed the lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. label Jul 2, 2018
@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 30, 2020
@neolit123
Copy link
Member

/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 30, 2020
@kikisdeliveryservice
Copy link
Member

Hi @neolit123

Enhancements Lead here. Any plans for this to graduate in 1.20?

Thanks,
Kirsten

@k8s-mirror-cluster-lifecycle-feature-re

@kikisdeliveryservice
Copy link
Member

Thanks, I will keep this as untracked, please let us know if anything changes so we can properly tracks & milestone this KEP.

@fejta-bot
Copy link

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/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 20, 2021
@neolit123
Copy link
Member

/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 20, 2021
@fejta-bot
Copy link

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

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 20, 2021
@neolit123
Copy link
Member

/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 20, 2021
@fejta-bot
Copy link

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

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 19, 2021
@k8s-mirror-cluster-lifecycle-feature-re

@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 19, 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 Oct 17, 2021
@neolit123
Copy link
Member

/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 Oct 17, 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 Jan 15, 2022
@neolit123 neolit123 added stage/stable Denotes an issue tracking an enhancement targeted for Stable/GA status and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. stage/beta Denotes an issue tracking an enhancement targeted for Beta status labels Jan 17, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature Categorizes issue or PR as related to a new feature. sig/cluster-lifecycle Categorizes an issue or PR as relevant to SIG Cluster Lifecycle. stage/stable Denotes an issue tracking an enhancement targeted for Stable/GA status tracked/no Denotes an enhancement issue is NOT actively being tracked by the Release Team
Projects
None yet
Development

Successfully merging a pull request may close this issue.