Skip to content
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

Upgrade cri-tools to 1.32.0 to sync up with the latest AKS version #11966

Merged
merged 1 commit into from
Jan 22, 2025

Conversation

CBL-Mariner-Bot
Copy link
Collaborator

@CBL-Mariner-Bot CBL-Mariner-Bot commented Jan 16, 2025

Merge Checklist

All boxes should be checked before merging the PR (just tick any boxes which don't apply to this PR)

  • The toolchain has been rebuilt successfully (or no changes were made to it)
  • The toolchain/worker package manifests are up-to-date
  • Any updated packages successfully build (or no packages were changed)
  • Packages depending on static components modified in this PR (Golang, *-static subpackages, etc.) have had their Release tag incremented.
  • Package tests (%check section) have been verified with RUN_CHECK=y for existing SPEC files, or added to new SPEC files
  • All package sources are available
  • cgmanifest files are up-to-date and sorted (./cgmanifest.json, ./toolkit/scripts/toolchain/cgmanifest.json, .github/workflows/cgmanifest.json)
  • LICENSE-MAP files are up-to-date (./LICENSES-AND-NOTICES/SPECS/data/licenses.json, ./LICENSES-AND-NOTICES/SPECS/LICENSES-MAP.md, ./LICENSES-AND-NOTICES/SPECS/LICENSE-EXCEPTIONS.PHOTON)
  • All source files have up-to-date hashes in the *.signatures.json files
  • sudo make go-tidy-all and sudo make go-test-coverage pass
  • Documentation has been updated to match any changes to the build system
  • Ready to merge

Summary

What does the PR accomplish, why was it needed?
cri-tools provide debugging and validation tools for Kubelet CRI, which includes:

  • crictl: CLI for kubelet CRI.
  • critest: validation test suites for kubelet CRI.

It's recommended to use the same cri-tools and Kubernetes minor version, because new features added to the Container Runtime Interface (CRI) may not be fully supported if they diverge. AKS currently supports k8s version v1.27 - v1.31 and will support v1.32 soon, in order to sync up with the latest AKS version, we need to upgrade cri-tools to the latest version v1.32.0. Additionally, our AKS tests will onboard critest for containerd validation and benchmarking, this upgrade will make sure all the feature s in CRI defined by k8s are fully tested.

Change Log
  • Upgrade cri-tools to 1.31.1 Sync up with the latest AKS
Does this affect the toolchain?

NO

Associated issues
  • #xxxx
Test Methodology

@CBL-Mariner-Bot CBL-Mariner-Bot requested a review from a team as a code owner January 16, 2025 22:45
@liunan-ms liunan-ms changed the title [AUTOPATCHER-CORE] Upgrade cri-tools to 1.32.0 to sync up with the latest AKS version Upgrade cri-tools to 1.32.0 to sync up with the latest AKS version Jan 17, 2025
@liunan-ms liunan-ms merged commit 598271d into 3.0-dev Jan 22, 2025
13 checks passed
@liunan-ms liunan-ms deleted the cblmargh/cri-tools-upgrade-to-1.32.0-3.0-dev branch January 22, 2025 19:43
SumitJenaHCL pushed a commit to SumitJenaHCL/azurelinux that referenced this pull request Jan 28, 2025
SumitJenaHCL pushed a commit to SumitJenaHCL/azurelinux that referenced this pull request Feb 24, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants