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

Kubeadm for Windows #995

Open
ksubrmnn opened this issue Apr 24, 2019 · 80 comments
Open

Kubeadm for Windows #995

ksubrmnn opened this issue Apr 24, 2019 · 80 comments
Assignees
Labels
kind/feature Categorizes issue or PR as related to a new feature. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. sig/cluster-lifecycle Categorizes an issue or PR as relevant to SIG Cluster Lifecycle. sig/windows Categorizes an issue or PR as relevant to SIG Windows. stage/alpha Denotes an issue tracking an enhancement targeted for Alpha status tracked/no Denotes an enhancement issue is NOT actively being tracked by the Release Team

Comments

@ksubrmnn
Copy link
Contributor

ksubrmnn commented Apr 24, 2019

Enhancement Description

  • One-line enhancement description (can be used as a release note): Kubeadm support for Windows
  • Kubernetes Enhancement Proposal: 20190424-kubeadm-for-windows
  • Primary contact (assignee): @benmoss
  • Responsible SIGs:
    /sig-windows
    /sig-cluster-lifecycle
  • Enhancement target (which target equals to which milestone):
    • Alpha release target 1.16
    • Beta release target: 1.18
    • GA release target: TODO
@neolit123
Copy link
Member

neolit123 commented Apr 24, 2019

/sig windows
/sig cluster-lifecycle

@k8s-ci-robot k8s-ci-robot added sig/windows Categorizes an issue or PR as relevant to SIG Windows. sig/cluster-lifecycle Categorizes an issue or PR as relevant to SIG Cluster Lifecycle. labels Apr 24, 2019
@neolit123 neolit123 added this to the v1.15 milestone Apr 24, 2019
@neolit123 neolit123 added kind/feature Categorizes issue or PR as related to a new feature. stage/alpha Denotes an issue tracking an enhancement targeted for Alpha status labels Apr 24, 2019
@kacole2 kacole2 added the tracked/yes Denotes an enhancement issue is actively being tracked by the Release Team label Apr 24, 2019
@craiglpeters craiglpeters added tracked/no Denotes an enhancement issue is NOT actively being tracked by the Release Team and removed tracked/yes Denotes an enhancement issue is actively being tracked by the Release Team labels May 1, 2019
@craiglpeters
Copy link
Contributor

craiglpeters commented May 1, 2019

@ksubrmnn, Enhancement Freeze for Kubernetes 1.15 has passed and this did not meet the deadline. This is now being removed from the 1.15 milestone and the tracking sheet. If there is a need for this to be in 1.15, please file an Enhancement Exception. Thank you.

@craiglpeters
Copy link
Contributor

craiglpeters commented May 1, 2019

/milestone clear

@k8s-ci-robot k8s-ci-robot removed this from the v1.15 milestone May 1, 2019
@michmike michmike added this to Backlog (v.1.15) in SIG-Windows May 3, 2019
@kacole2 kacole2 added tracked/yes Denotes an enhancement issue is actively being tracked by the Release Team and removed tracked/no Denotes an enhancement issue is NOT actively being tracked by the Release Team labels May 6, 2019
@kacole2 kacole2 added this to the v1.15 milestone May 6, 2019
@craiglpeters
Copy link
Contributor

craiglpeters commented May 29, 2019

Hi @ksubrmnn . Code Freeze is Thursday, May 30th 2019 @ EOD PST. All enhancements going into the release must be code-complete, including tests, and have docs PRs open.

Please list all current k/k PRs so they can be tracked going into freeze. If the PRs aren't merged by freeze, this feature will slip for the 1.15 release cycle. Only release-blocking issues and PRs will be allowed in the milestone.

If you know this will slip, please reply back and let us know. Thanks!

@michmike
Copy link
Contributor

michmike commented May 30, 2019

@craiglpeters according to the KEP for kubeadm for 1.15, we were not going to add any more tests beyond unit tests. are we good on this area? thanks!
cc: @ksubrmnn

@makoscafee
Copy link
Member

makoscafee commented May 30, 2019

Hey, @michmike @ksubrmnn 👋 I'm the v1.15 docs Lead.
Does this enhancement require any new docs (or modifications)?

Sorry for getting to you late, Code Freeze is Thursday, May 30th 2019 @ EOD PST It would be great to have a placeholder PR by then can be just empty PR with title and description. Let me know if you have any questions!

@PatrickLang PatrickLang moved this from Backlog (v.1.15) to In Progress+Review in SIG-Windows May 30, 2019
@craiglpeters
Copy link
Contributor

craiglpeters commented May 30, 2019

@michmike and @ksubrmnn yes agreed that unit tests are good for alpha. I still need to know which k/k PRs to track for this issue. It's now being marked as At Risk in the 1.15 Enhancement Tracking Sheet. Is there high confidence these will be merged by EOD PST today? After this point, only release-blocking issues and PRs will be allowed in the milestone with an exception.

@ksubrmnn
Copy link
Contributor Author

ksubrmnn commented May 30, 2019

@craiglpeters See kubernetes/kubeadm#1393

We are still on track for alpha. I will fix up kubernetes/kubernetes#78324 and it will get merged today.

@ksubrmnn
Copy link
Contributor Author

ksubrmnn commented May 30, 2019

Docs PR open: kubernetes/website#14644

@michmike
Copy link
Contributor

michmike commented May 30, 2019

@craiglpeters we will continue working on this. if we can get an exception, it will make it into 1.15 and if not it will come later. the code changes are good, but there is still lots of documentation work left.

@PatrickLang
Copy link
Contributor

PatrickLang commented May 30, 2019

also related kubernetes/kubernetes#78189

@craiglpeters
Copy link
Contributor

craiglpeters commented May 31, 2019

Hi @ksubrmnn, tomorrow is code freeze (one day delay) for the 1.15 release cycle. The k/k PRs have not yet been merged. It's now being marked as At Risk in the 1.15 Enhancement Tracking Sheet. Is there high confidence these will be merged by EOD PST tomorrow? After this point, only release-blocking issues and PRs will be allowed in the milestone with an exception.

@kikisdeliveryservice
Copy link
Member

kikisdeliveryservice commented Sep 14, 2020

Thanks for the fast update @marosset & @neolit123 ! Much appreciated!!

@fejta-bot
Copy link

fejta-bot commented Dec 13, 2020

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 Dec 13, 2020
@marosset
Copy link
Contributor

marosset commented Dec 14, 2020

/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 Dec 14, 2020
@fejta-bot
Copy link

fejta-bot commented Mar 14, 2021

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

neolit123 commented Mar 15, 2021

/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 Mar 15, 2021
@marosset
Copy link
Contributor

marosset commented Apr 7, 2021

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

fejta-bot commented Apr 7, 2021

Enhancement issues opened in kubernetes/enhancements should never be marked as frozen.
Enhancement Owners can ensure that enhancements stay fresh by consistently updating their states across release cycles.

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

fejta-bot commented Jul 6, 2021

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

neolit123 commented Jul 6, 2021

/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 6, 2021
@k8s-triage-robot
Copy link

k8s-triage-robot commented Oct 4, 2021

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

neolit123 commented Oct 4, 2021

/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 4, 2021
@k8s-triage-robot
Copy link

k8s-triage-robot commented Jan 2, 2022

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 2, 2022
@neolit123
Copy link
Member

neolit123 commented Jan 3, 2022

@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 3, 2022
@k8s-triage-robot
Copy link

k8s-triage-robot commented Apr 3, 2022

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 Apr 3, 2022
@neolit123 neolit123 added lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Apr 4, 2022
@marosset marosset removed this from Backlog (issues) in SIG-Windows Sep 21, 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. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. sig/cluster-lifecycle Categorizes an issue or PR as relevant to SIG Cluster Lifecycle. sig/windows Categorizes an issue or PR as relevant to SIG Windows. stage/alpha Denotes an issue tracking an enhancement targeted for Alpha status tracked/no Denotes an enhancement issue is NOT actively being tracked by the Release Team
Projects
Development

No branches or pull requests