Skip to content
This repository has been archived by the owner on Mar 14, 2024. It is now read-only.

WINC-602: [wmcb] Support Windows Server 2022 #316

Conversation

saifshaikh48
Copy link
Contributor

This requires upgrading the pause image to 3.6
which has support for Windows Server 2022.

@selansen
Copy link

selansen commented Feb 3, 2022

But the same Pause will be used now in other windows server version too. Can we make PR title generic like "Upgrade Pause image to 3.6"

@sebsoto
Copy link
Contributor

sebsoto commented Feb 3, 2022

/approve

@@ -46,7 +46,7 @@ const (
// this is used to parse the kubelet args
kubeletSystemdName = "kubelet.service"
// kubeletPauseContainerImage is the location of the image we will use for the kubelet pause container
kubeletPauseContainerImage = "mcr.microsoft.com/oss/kubernetes/pause:3.4.1"
kubeletPauseContainerImage = "mcr.microsoft.com/oss/kubernetes/pause:3.6"

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should we be using 3.5 since we're still on 1.22?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Best to always stay at the latest to catch base image fixes.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't think pause images are tied to a specific kube version

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I thought they might be because of this doc: https://kubernetes.io/docs/setup/production-environment/windows/intro-windows-in-kubernetes/#pause-container
But makes sense to have latest. I'm ok with 3.6

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We should keep in mind we are moving to the version that adds support for 2022. 3.5 might not support it.

@aravindhp
Copy link
Contributor

But the same Pause will be used now in other windows server version too. Can we make PR title generic like "Upgrade Pause image to 3.6"

@selansen this is the pattern we have been following. Please see #258. We want to call out that we are adding support for a new Windows version explicitly by upgrading the pause image.

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Feb 3, 2022
@mansikulkarni96
Copy link
Member

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Feb 3, 2022
@saifshaikh48
Copy link
Contributor Author

/test e2e-wmcb
/test aws-e2e-ccm-install

@alinaryan
Copy link

/lgtm

1 similar comment
@jrvaldes
Copy link
Contributor

jrvaldes commented Feb 3, 2022

/lgtm

@aravindhp
Copy link
Contributor

/hold

Until we figure out the hybrid-overlay test failure

@openshift-ci openshift-ci bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Feb 3, 2022
@selansen
Copy link

selansen commented Feb 3, 2022

/lgtm

@aravindhp
Copy link
Contributor

/hold cancel
/retest-required

@openshift-ci openshift-ci bot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Feb 7, 2022
@openshift-bot
Copy link

/retest-required

Please review the full test history for this PR and help us cut down flakes.

@aravindhp
Copy link
Contributor

aravindhp commented Feb 7, 2022

/hold

unit test is failing due to a change introduced in this PR.

@openshift-ci openshift-ci bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Feb 7, 2022
This requires upgrading the pause image to 3.6 which has support for
Windows Server 2022.
@openshift-ci openshift-ci bot removed the lgtm Indicates that a PR is ready to be merged. label Feb 7, 2022
@aravindhp
Copy link
Contributor

/hold cancel

Unit test has been fixed

@openshift-ci openshift-ci bot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Feb 7, 2022
@jrvaldes
Copy link
Contributor

jrvaldes commented Feb 8, 2022

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Feb 8, 2022
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Feb 8, 2022

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: alinaryan, jrvaldes, mansikulkarni96, saifshaikh48, sebsoto, selansen

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 /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@saifshaikh48
Copy link
Contributor Author

/cherry-pick release-4.10

@openshift-cherrypick-robot

@saifshaikh48: once the present PR merges, I will cherry-pick it on top of release-4.10 in a new PR and assign it to you.

In response to this:

/cherry-pick release-4.10

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.

@saifshaikh48
Copy link
Contributor Author

/cherry-pick release-4.9

@openshift-cherrypick-robot

@saifshaikh48: once the present PR merges, I will cherry-pick it on top of release-4.9 in a new PR and assign it to you.

In response to this:

/cherry-pick release-4.9

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.

@saifshaikh48
Copy link
Contributor Author

/cherry-pick community-4.9

@openshift-cherrypick-robot

@saifshaikh48: once the present PR merges, I will cherry-pick it on top of community-4.9 in a new PR and assign it to you.

In response to this:

/cherry-pick community-4.9

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.

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Feb 8, 2022

@saifshaikh48: all tests passed!

Full PR test history. Your PR dashboard.

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. I understand the commands that are listed here.

@openshift-cherrypick-robot

@saifshaikh48: new pull request created: #332

In response to this:

/cherry-pick release-4.9

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.

@openshift-cherrypick-robot

@saifshaikh48: new pull request created: #333

In response to this:

/cherry-pick community-4.9

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.

@openshift-cherrypick-robot

@saifshaikh48: new pull request created: #334

In response to this:

/cherry-pick release-4.10

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.

@saifshaikh48
Copy link
Contributor Author

/cherry-pick community-4.8

@saifshaikh48
Copy link
Contributor Author

/cherry-pick release-4.8

@openshift-cherrypick-robot

@saifshaikh48: new pull request created: #335

In response to this:

/cherry-pick community-4.8

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.

@openshift-cherrypick-robot

@saifshaikh48: new pull request created: #336

In response to this:

/cherry-pick release-4.8

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 subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. lgtm Indicates that a PR is ready to be merged.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

10 participants