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

Windows machine image #30

Closed
akutz opened this issue Sep 9, 2019 · 8 comments
Closed

Windows machine image #30

akutz opened this issue Sep 9, 2019 · 8 comments
Assignees
Labels
lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness.

Comments

@akutz
Copy link
Contributor

akutz commented Sep 9, 2019

Per @rhockenbury and kubernetes-sigs/cluster-api-provider-vsphere#525:

K8s windows node support has been GA since 1.14. Are there plans to produce a CAPV windows machine image?

@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 Dec 8, 2019
@detiber
Copy link
Member

detiber commented Dec 9, 2019

/lifecycle frozen

@k8s-ci-robot k8s-ci-robot 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 Dec 9, 2019
@jsturtevant
Copy link
Contributor

/assign

@jsturtevant
Copy link
Contributor

I have started working on this for the Windows Proposal in CAPI: kubernetes-sigs/cluster-api#3616

@jsturtevant
Copy link
Contributor

I just noticed this is not just windows image but specifically for CAPV. I have added the configuration scripts which would enable CAPV in #382 but did this for Azure packer configuration first.

Should this issue be considered for Configuration or keep is specifcally for CAPV? If so would some one familiar with CAPV be able to take a look at the PR to see if it meets needs of CAPV? I am happy to work with someone to make sure the configuration I started will work for CAPV.

@benmoss
Copy link

benmoss commented Sep 24, 2020

I did a spike a long while ago to get this working on AWS master...benmoss:master

@jsturtevant
Copy link
Contributor

Vsphere and Azure have been added with aws ami in progress #442

/close

@k8s-ci-robot
Copy link
Contributor

@jsturtevant: Closing this issue.

In response to this:

Vsphere and Azure have been added with aws ami in progress #442

/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/frozen Indicates that an issue or PR should not be auto-closed due to staleness.
Projects
None yet
Development

No branches or pull requests

6 participants