WINC-805: Add support for Windows Server 2022 in AWS#1091
Conversation
|
Skipping CI for Draft Pull Request. |
|
/test azure-e2e-operator |
|
/test aws-e2e-operator |
|
/test lint |
|
/test aws-e2e-upgrade |
saifshaikh48
left a comment
There was a problem hiding this comment.
Code changes lgtm, question on docs
|
Can you pls add a few lines in the description section? |
|
Don't we need to update the image deployed for networking test here |
8abf347 to
7193a6d
Compare
|
/test aws-e2e-operator |
2 similar comments
|
/test aws-e2e-operator |
|
/test aws-e2e-operator |
|
/test aws-e2e-operator |
1968bfd to
004f74b
Compare
|
/test aws-e2e-operator |
|
/test aws-e2e-upgrade |
1 similar comment
|
/test aws-e2e-upgrade |
|
/test aws-e2e-operator Build src image failed |
|
/test aws-e2e-operator |
|
/test aws-e2e-ccm-install |
|
/test aws-e2e-upgrade |
|
/test aws-e2e-upgrade |
|
Rebased with: |
92c0a91 to
64f5930
Compare
| patchData, meta.PatchOptions{}) | ||
| if err != nil { | ||
| return errors.Wrapf(err, "error removing version annotation from node %s", nc.node.GetName()) | ||
| // Check version annotation and remove iff present |
There was a problem hiding this comment.
How does this commit relate to adding Server 2022 support?
|
/hold To investigate the issue with AWS EC2 metadata endpoint not available. |
This commit declares support for Windows Server 2022 in the documentation.
This commit updates the hack/machineset.sh script to use Windows Server 2022 base image without containers for AWS machineSets. In addition, re-arrange the aws cli command that fetch the AMI id with a multiline for better readability.
This commit updates the AWS's EC2 AMI to use Windows Server 2022 base image without container runtime. The container runtime (containerd) is installed by WMCO. It also leverages the environment variable introduced in openshift/release#29791 to allow a parameter-based configuration for Windows Server version, where the machine and container images can be adjusted in the e2e test suite. In addition, adjusts the logic for PowerShell cmdlets to avoid escaping the double-quotes when default shell is PowerShell to taking into account the Windows Server version.
|
/test aws-e2e-upgrade |
|
/test aws-e2e-operator |
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: jrvaldes The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
This change introduces a hack to circumvent the routing issue in Windows Server 2022 running the EC2Launch V2 agent where the instance metadata endpoint is not available after hybrid-overlay is running as a Windows service. See ovn-kubernetes/ovn-kubernetes#3119
|
/test aws-e2e-upgrade |
|
/test aws-e2e-operator |
|
@jrvaldes: The following tests failed, say
Full PR test history. Your PR dashboard. DetailsInstructions 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. I understand the commands that are listed here. |
|
/close This hack does not work. For one EC2Launch v2 is a service and we should be restarting that and not just executing the binary. Further more restarting the service does not result in the routes being recreated as the services loops waiting for an IP address: |
|
PR needs rebase. DetailsInstructions 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. |
|
@aravindhp: Closed this PR. DetailsIn 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. |
This PR updates the AWS's EC2 AMI to use Windows Server 2022
Base image without Docker container runtime, as the container runtime
(containerd) is installed by WMCO.
Leverage the environment variable introduced in the release job configuration to use Windows Server 2019 as machine and container images for the
aws-e2e-operatortest