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
Adds Windows support for etcd image #92433
Adds Windows support for etcd image #92433
Conversation
The k8s control plane does not run on windows, does it? What's the purpose of this? |
/assign @yliaog |
i think it is for e2e tests |
9794936
to
caa8ff5
Compare
caa8ff5
to
f5f6fe4
Compare
Yes, pretty much. There are some tests that require the etcd image. The test |
f5f6fe4
to
c0279d5
Compare
c0279d5
to
24e4111
Compare
/lgtm |
/retest |
/assign @jpbetz |
/milestone v1.23 It looks like this PR has been ready to merge since v1.21 timeframe. |
I never got an answer to my original question: "The k8s control plane does not run on windows, does it? What's the purpose of this?" #92433 (comment) |
e59d140
to
6e82ee3
Compare
Hi 👋 I'm the bug triage shadow. I wanted to check in and see if this is targeted for 1.23 milestone. Attempting to nudge the conversation forward, @claudiubelu I wanted to bring attention to a question asked earlier in the thread #92433 (comment) . |
This is used in one of the e2e conformance tests. |
6e82ee3
to
6137149
Compare
6137149
to
838af5a
Compare
We can use docker buildx in order to build and push Windows images from the same Linux node, as long as the Dockerfile does not have any RUN commands in the Windows step. We also need to create a non-default builder instance in order to be able to build and push Windows images. The Windows images have to be built and pushed directly to the registry. For Windows containers without Hyper-V isolation, the host OS Version and the Container OS Version need to match, which is why we added multiple Windows OS Versions to the building process. For the manifest list, we need to also annotate the Windows OS Version, so the Windows nodes will be able to pull the proper image from the manifest list. Adds support for Windows OS Versions: 1809, 2004, 20H2, ltsc2022. Bumped etcd image revision.
838af5a
to
c4fc9bb
Compare
@jpbetz can you take another look at this? |
Ah, it's for the aggregator. That makes sense. Thanks for explaining. /lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: claudiubelu, jpbetz The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
What type of PR is this?
/kind feature
/sig windows
What this PR does / why we need it:
We can use
docker buildx
in order to build and push Windows images from the same Linux node, as long as the Dockerfile does not have anyRUN
commands in the Windows step.We also need to create a non-default builder instance in order to be able to build and push Windows images.
The Windows images have to be built and pushed directly to the registry.
For Windows containers without Hyper-V isolation, the host OS Version and the Container OS Version need to match, which is why we added multiple Windows OS Versions to the building process.
Adds support for Windows OS Versions: 1809, 2004, 20H2, 2022.
Bumped etcd image revision to 2.
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?:
Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.: