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

compatibility with windows #3771

Closed
daksha25 opened this issue Nov 27, 2018 · 8 comments
Closed

compatibility with windows #3771

daksha25 opened this issue Nov 27, 2018 · 8 comments
Labels
lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.

Comments

@daksha25
Copy link

hi,
Will it work if want to set up windows cluster?

@rhockenbury
Copy link
Contributor

No. I would suggest looking at https://github.com/pablodav/kubernetes-for-windows-quickstart for running hybrid clusters.

@ant31
Copy link
Contributor

ant31 commented Nov 27, 2018

@pablodav what's missing to merge your windows fork?

@pablodav
Copy link
Contributor

There is still missing a stable flanned version working.

Then I will start working on more tests / stabilization of the playbooks.
I'm would love to have automated tests here, but I don't have enough free time to work on it myself.

Then I will start working on kubespraynation of them.... :)

@rhockenbury
Copy link
Contributor

For what it's worth, flannel has been much more stable on windows server 2019.

Also, would be interested in hearing about the general strategy for porting windows support into kubespray. For instance, would the initial integration be done through a seperate windows role, or would the windows support need to be integrated into each role for the seperate components?

I would imagine the place to start is updating the kubespray test cases to work on hybrid clusters, and then getting support integrated into the CI harness. Looks to me like adding a new test file, and then updates for generating the inventory file with a seperate host group for windows nodes. @ant31 Any first impressions on level of effort, or recommended starting approaches?

@pablodav
Copy link
Contributor

I have noticed there is also #2889 disussing similar things or same things.

@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
@rhockenbury
Copy link
Contributor

/close

@k8s-ci-robot
Copy link
Contributor

@rhockenbury: Closing this issue.

In response to this:

/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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.
Projects
None yet
Development

No branches or pull requests

6 participants