From cc2a31c31f5b251a424cfe14e5023a810e0aae8b Mon Sep 17 00:00:00 2001 From: Amim Knabben Date: Fri, 4 Oct 2024 16:27:10 -0300 Subject: [PATCH] Updating CAPZ master informing job to Windows 2022 --- .../kubernetes-sigs/sig-windows/release-master-windows.yaml | 5 +---- 1 file changed, 1 insertion(+), 4 deletions(-) diff --git a/config/jobs/kubernetes-sigs/sig-windows/release-master-windows.yaml b/config/jobs/kubernetes-sigs/sig-windows/release-master-windows.yaml index e87edea7b162..53aacee0f756 100644 --- a/config/jobs/kubernetes-sigs/sig-windows/release-master-windows.yaml +++ b/config/jobs/kubernetes-sigs/sig-windows/release-master-windows.yaml @@ -81,7 +81,7 @@ periodics: preset-dind-enabled: "true" preset-kind-volume-mounts: "true" preset-capz-windows-common: "true" - preset-capz-windows-2019: "true" + preset-capz-windows-2022: "true" preset-capz-containerd-1-7-latest: "true" preset-azure-community: "true" extra_refs: @@ -119,9 +119,6 @@ periodics: limits: cpu: 2 memory: "9Gi" - env: - - name: IMAGE_VERSION - value: "127.1.20230417" # pin the Windows nodes to a specific OS patch version while investigating an issue with container updates annotations: fork-per-release: "true" fork-per-release-replacements: "KUBERNETES_VERSION=latest -> KUBERNETES_VERSION=latest-{{.Version}}"