-
Notifications
You must be signed in to change notification settings - Fork 409
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
Comments
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
/lifecycle frozen |
/assign |
I have started working on this for the Windows Proposal in CAPI: kubernetes-sigs/cluster-api#3616 |
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. |
I did a spike a long while ago to get this working on AWS master...benmoss:master |
Vsphere and Azure have been added with aws ami in progress #442 /close |
@jsturtevant: Closing this issue. In response to this:
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. |
Per @rhockenbury and kubernetes-sigs/cluster-api-provider-vsphere#525:
The text was updated successfully, but these errors were encountered: