dev-docs: add script for updating k8s versions in workflow files (#3899)

* ci: use v prefix for k8s version in e2e daily

* dev-docs: suggest script for k8s version bump in workflows
This commit is contained in:
Markus Rudy 2025-07-31 11:51:45 +02:00 committed by GitHub
parent 8bfffb6eeb
commit 7a7559e4e8
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
2 changed files with 15 additions and 2 deletions

View file

@ -45,7 +45,7 @@ jobs:
fail-fast: false fail-fast: false
max-parallel: 5 max-parallel: 5
matrix: matrix:
kubernetesVersion: ["1.30"] # This should correspond to the current default k8s minor. kubernetesVersion: ["v1.31"] # This should correspond to the current default k8s minor.
attestationVariant: ["gcp-sev-es", "gcp-sev-snp", "azure-sev-snp", "azure-tdx", "aws-sev-snp"] attestationVariant: ["gcp-sev-es", "gcp-sev-snp", "azure-sev-snp", "azure-tdx", "aws-sev-snp"]
refStream: ["ref/main/stream/debug/?", "ref/release/stream/stable/?"] refStream: ["ref/main/stream/debug/?", "ref/release/stream/stable/?"]
test: ["sonobuoy quick"] test: ["sonobuoy quick"]

View file

@ -27,7 +27,20 @@ curl -qL https://mcr.microsoft.com/v2/oss/kubernetes/azure-cloud-node-manager/ta
Normally renovate will handle the upgrading of Kubernetes dependencies. Normally renovate will handle the upgrading of Kubernetes dependencies.
Also, don't forget to update the Kubernetes versions tested in the CI. (e.g. release, weekly E2E tests) ## Update e2e tests
Run the following script to update the k8s versions used in the e2e workflows, adjusting the versions to what you're upgrading to.
```sh
next=v1.33
current=v1.32
old=v1.31
oldold=v1.30
sed -i -e "s/$current/$next/g" -e "s/$old/$current/g" -e "s/$oldold/$old/g" \
.github/workflows/e2e-test-daily.yml \
.github/workflows/e2e-test-weekly.yml \
.github/workflows/e2e-test-release.yml
```
## Test the new Kubernetes version ## Test the new Kubernetes version