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 #2889

Closed
ant31 opened this issue Jun 14, 2018 · 18 comments
Closed

Support windows #2889

ant31 opened this issue Jun 14, 2018 · 18 comments

Comments

@ant31
Copy link
Contributor

ant31 commented Jun 14, 2018

follow up for #2864.

@ant31
Copy link
Contributor Author

ant31 commented Jun 14, 2018

cc @pablodav

@pablodav
Copy link
Contributor

Thanks @ant31 , will comment here for news.
Now working in updates for windows 1803 and testing.

@pablodav
Copy link
Contributor

@pablodav
Copy link
Contributor

pablodav commented Jun 20, 2018

Hi @ant31

I think I have finished most of the work, now I think all steps are working properly to try in a preprod environment.

I have also created:
https://github.com/pablodav/kubernetes-for-windows-quickstart

It will help to test the roles and then a good base to start working on changes before start working on a merge to kubespray directly.

Could you have a look / test it?

@pablodav
Copy link
Contributor

pablodav commented Jul 3, 2018

hope #2956 could be merged, as without these changes we can't continue working on this issue. (I'm will continue working on my separate project while it is not merged)

@ashishtechie
Copy link

@pablodav just tried to follow this issue. I am looking to create a hybrid cluster too, just wanted to see if you were able to push the windows support to kube-spray?

Also, what networking plugin did you end up using for windows and linux

@pablodav
Copy link
Contributor

My own tracking is here: https://github.com/pablodav/kubernetes-for-windows

For now I have completed the tests only with flannel, but there are some things not 100% stabilized yet:
pablodav/kubernetes-for-windows#10

I haven't had time to test with ovn, I think kubespray doesn't support it yet.
pablodav/kubernetes-for-windows#3

calico doesn't looks to be supported at all in windows.
pablodav/kubernetes-for-windows#2

More discussion:
pablodav/kubernetes-for-windows#13

And something that I haven't looked at all yet but could be good to have before moving all this stuff to kubespray:
pablodav/kubernetes-for-windows#12

Note: the project already works and uses kubespray.

This was referenced Dec 13, 2018
@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 Apr 11, 2019
@fejta-bot
Copy link

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

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 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 May 11, 2019
@okamototk
Copy link
Contributor

okamototk commented May 11, 2019

Kubernetes 1.14.1 supports Window Container as production.

IMO, it's time to support Windows Containers.
When I challenged Windows Container by manual for kubernetes, I have some of problem.
In the first, fixed these problem, next I'll create PR for this.

  1. ingress nginx default-backend service has no endpoints. Then, kubelet on Windows are outputting error message continuously.
  1. Some of ds will be scheduled on Windows Node such as
  • kube-flannel-ds-amd64
  • nodelocaldns
  • kube-proxy

Linux ds should be fixed on Linux Node by nodeSelector.

  1. flannel's network configuration should be configurable. Especiall, VNI and Port.

PR for above improvement is #4746.

@daschott
Copy link

@okamototk @pablodav FYI in v1.15 there is also work on kubeadm to add Windows node support: kubernetes/enhancements#994

@pablodav
Copy link
Contributor

great news, thanks for notifying!

@okamototk
Copy link
Contributor

@okamototk @pablodav FYI in v1.15 there is also work on kubeadm to add Windows node support: kubernetes/enhancements#994

Thanks, after 1.15 will be released, I'll check it.

@ant31
Copy link
Contributor Author

ant31 commented May 16, 2019

/remove-lifecycle stale

@fejta-bot
Copy link

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

@k8s-ci-robot
Copy link
Contributor

@fejta-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/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.

@madhu1992blue
Copy link

madhu1992blue commented Feb 21, 2020

/reopen
/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 Feb 21, 2020
@k8s-ci-robot
Copy link
Contributor

@madhu1992blue: You can't reopen an issue/PR unless you authored it or you are a collaborator.

In response to this:

/reopen

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

8 participants