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

Support Windows Server Containers for K8s #116

Closed
michmike opened this issue Oct 6, 2016 · 69 comments
Closed

Support Windows Server Containers for K8s #116

michmike opened this issue Oct 6, 2016 · 69 comments
Assignees
Labels
kind/feature Categorizes issue or PR as related to a new feature. sig/node Categorizes an issue or PR as relevant to SIG Node. sig/windows Categorizes an issue or PR as relevant to SIG Windows. 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
Milestone

Comments

@michmike
Copy link
Contributor

michmike commented Oct 6, 2016

Description

Microsoft, in collaboration with Docker, is introducing a new feature called Windows Server Containers, which enables Docker containers to run on Windows. SIG-Windows would like to enhance Kubernetes to support Windows Server Containers (and Windows Server 2016 as the operating system of choice for the windows-based kubelet). With this feature, customers will be able to run Windows-based and .NET-based applications inside containers on Kubernetes. Kubernetes will be the first fully functional cross-platform cluster manager.

Feature Description

  • One-line feature description (can be used as a release note): Support for Windows Server Containers
  • Primary contact (assignee): @michmike
  • Responsible SIGs: sig-windows
  • Kubernetes Enhancement Proposal (KEP): Create KEP for Windows Node Support #676
  • Reviewer(s) - (for LGTM) recommend having 2+ reviewers (at least one from code-area OWNERS file) agreed to review. Reviewers from multiple companies preferred: @brendandburns, @JiangtianLi, @alinbalutoiu
  • Approver (likely from SIG/area to which feature belongs): @michmike
  • Feature target (which target equals to which milestone):
    • Beta release target 1.9
    • GA release target 1.14

SIG-Windows approved GA release criteria: https://docs.google.com/document/d/1YkLZIYYLMQhxdI2esN5PuTkhQHhO0joNvnbHpW68yg8/edit (old)

New KEP release criteria:
#676

@michmike
Copy link
Contributor Author

michmike commented Oct 6, 2016

cc: @sarahnovotny, @idvoretskyi, and @kubernetes/sig-node

@magicwang-cn
Copy link

magicwang-cn commented Oct 7, 2016

@kubernetes/huawei

@idvoretskyi idvoretskyi added the sig/windows Categorizes an issue or PR as relevant to SIG Windows. label Oct 7, 2016
@idvoretskyi idvoretskyi added this to the v1.5 milestone Oct 7, 2016
@luxas
Copy link
Member

luxas commented Oct 9, 2016

@michmike
Copy link
Contributor Author

michmike commented Oct 9, 2016

thanks for sending us this @luxas

@idvoretskyi
Copy link
Member

idvoretskyi commented Nov 2, 2016

Marked as "Alpha" per @michmike request.

@idvoretskyi
Copy link
Member

idvoretskyi commented Dec 13, 2016

@michmike can you confirm that this item targets beta in 1.6?

@michmike
Copy link
Contributor Author

michmike commented Dec 13, 2016

@idvoretskyi , yes that's right. thanks!
we will be in beta for v1.6

@idvoretskyi idvoretskyi modified the milestones: v1.6, next-milestone Dec 13, 2016
@idvoretskyi idvoretskyi added stage/beta Denotes an issue tracking an enhancement targeted for Beta status and removed (deprecated) alpha-in-1.5 labels Dec 13, 2016
k8s-github-robot pushed a commit to kubernetes/kubernetes that referenced this issue Jan 23, 2017
Automatic merge from submit-queue

Powershell script to start kubelet and kube-proxy

**What this PR does / why we need it**:
This PR adds a powershell script to run kubelet and kube-proxy on Windows. It expects the required arguments like `API Server` location and uses appropriate defaults.

**Which issue this PR fixes** : 
fixes # #34270

**Special notes for your reviewer**:
This PR is for supporting Windows Server Containers for k8s, the work for which is covered under kubernetes/enhancements#116
This PR should be merged after #31707 and #36079 PRs are merged

**Release note**:

```release-note
```
@michmike
Copy link
Contributor Author

michmike commented Jan 16, 2019

@spiffxp should we mark this as "Tracked/yes" now for v1.14 since we also have the KEP

@claurence
Copy link

claurence commented Jan 16, 2019

@michmike - targeting stable for 1.14 correct?

@michmike
Copy link
Contributor Author

michmike commented Jan 17, 2019

@claurence that is accurate.

@claurence claurence 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 Jan 22, 2019
@PatrickLang PatrickLang added this to Backlog (v1.14) in SIG-Windows Jan 29, 2019
@michmike
Copy link
Contributor Author

michmike commented Jan 30, 2019

KEP was approved today for stable release with 1.14

@lledru
Copy link
Member

lledru commented Feb 25, 2019

Hello, 1.14 enhancement shadow here. Code Freeze is March 7th and all PRs must be merged by then to your issue to make the 1.14 release. What open K/K PRs do you still have that need to merge? Thanks

@michmike
Copy link
Contributor Author

michmike commented Feb 25, 2019

@lledru we have some work that's underway and includes a few PRs. you can see our tracking board for 1.14 here. https://github.com/orgs/kubernetes/projects/8

@michmike michmike moved this from Backlog (v1.14) to 1.14 release Blocking (Windows GA, gMSA alpha) in SIG-Windows Feb 28, 2019
@craiglpeters
Copy link
Contributor

craiglpeters commented Mar 1, 2019

The placeholder Documentation PR is in place

@claurence
Copy link

claurence commented Mar 5, 2019

@michmike looking at that tracking board is everything in the 1.14 release blocking column what should be merged by code freeze? it looks like if I'm interpreting that correctly that is 9 open PRs in K/K that need to be merged by Friday?

@michmike
Copy link
Contributor Author

michmike commented Mar 5, 2019

@claurence that is correct. it is going to be a tight squeeze. a few of those PRs are ready to be merged today already.

@michmike
Copy link
Contributor Author

michmike commented Mar 19, 2019

3 years after the forming of SIG-Windows, we are pleased to announce that Kubernetes v1.14 will include stable support for windows

/close

@k8s-ci-robot
Copy link
Contributor

k8s-ci-robot commented Mar 19, 2019

@michmike: Closing this issue.

In response to this:

3 years after the forming of SIG-Windows, we are pleased to announce that Kubernetes v1.14 will include stable support for windows

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

SIG-Windows automation moved this from 1.14 Release Blocking (Windows GA, gMSA alpha) to Done (v1.15) Mar 19, 2019
@michmike michmike moved this from Done (v1.15) to Done (v.1.14) in SIG-Windows Mar 19, 2019
@kacole2 kacole2 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 Jul 15, 2019
ingvagabund pushed a commit to ingvagabund/enhancements that referenced this issue Apr 2, 2020
enhancements/template: Fix openshift-docs links
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/node Categorizes an issue or PR as relevant to SIG Node. sig/windows Categorizes an issue or PR as relevant to SIG Windows. 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

No branches or pull requests