リリース

CRI-O v1.35.1 fixes critical systemd container issues with user namespaces and adds TLS configuration options for API servers.

• breakingTest systemd workloads with user namespaces

  A regression in v1.35.0 broke systemd containers when hostUsers: false is set. This patch fixes it, but if you're running v1.35.0, upgrade immediately and test any systemd workloads that use user namespace isolation to ensure they start properly.

• enhancementConfigure TLS settings for production security

  New TLS configuration options let you harden streaming and metrics server security. Add tls_min_version and tls_cipher_suites to your [crio.api] section to enforce TLS 1.3 and strong cipher suites in production environments.

• enhancementVerify runc v1.4.0 compatibility

  The update to runc v1.4.0 brings performance improvements and bug fixes. Test your container workloads, especially those using advanced features like cgroups v2 or checkpoint/restore, to ensure compatibility with the new runtime version.

CRI-O v1.34.6 is a maintenance release with no functional changes, dependencies, or fixes - purely a version bump from v1.34.5.

• enhancementSkip this release unless forced by policy

  This release contains zero functional changes. Stay on v1.34.5 unless your organization requires running the latest patch version for compliance reasons. Save the upgrade effort for a release that brings actual improvements.

Kubernetes v1.35.2 is a patch release that provides stability and bug fixes for the v1.35 series, maintaining compatibility while addressing issues discovered in production environments.

• enhancementPlan routine patch upgrade

  This is a standard patch release with stability fixes. Schedule upgrade during your next maintenance window using standard rolling update procedures. Test in non-production environments first, but expect minimal risk as this maintains full compatibility with v1.35.x.

• enhancementUpdate container registry references

  Update your deployment manifests, Helm charts, and CI/CD pipelines to reference the new v1.35.2 container images. All images maintain the same registry.k8s.io paths with updated version tags.

Kubernetes v1.32.13 is a patch release focused on bug fixes and security improvements for the stable v1.32 series, maintaining backward compatibility.

• securityApply Security Patch Immediately

  This patch release likely includes critical security fixes. Schedule immediate upgrades for production clusters, especially if you're running earlier v1.32.x versions. Test in staging first, then roll out to production with standard maintenance windows.

• enhancementUpdate Container Images and Binaries

  Pull the latest v1.32.13 container images and update node binaries across your infrastructure. This is a straightforward in-place upgrade that maintains API compatibility. Update your CI/CD pipelines to reference the new image tags.

• enhancementVerify Multi-Architecture Support

  If running mixed-architecture clusters, ensure all architectures (amd64, arm64, ppc64le, s390x) are updated consistently. The manifest lists support automatic architecture selection, but verify your deployment automation handles this correctly.

Kubernetes v1.33.9 is a patch release providing critical bug fixes and stability improvements. This version maintains backward compatibility while addressing operational issues in the 1.33 branch.

• enhancementSchedule routine patch upgrade

  This is a standard patch release containing bug fixes and stability improvements. Plan to upgrade from earlier 1.33.x versions during your next maintenance window. Test in non-production environments first and follow your standard rolling update procedures.

• enhancementVerify multi-architecture support

  All container images now support manifest lists across amd64, arm64, ppc64le, and s390x architectures. If you're running mixed-architecture clusters, validate that your deployment tooling properly pulls the correct architecture-specific images.

Kubernetes v1.34.5 is a patch release providing standard bug fixes and stability improvements for the 1.34 series, with no major feature changes or breaking modifications.

• enhancementSchedule routine upgrade during maintenance window

  As a patch release, v1.34.5 contains stability and bug fixes that should be applied during your next scheduled maintenance window. Test in non-production environments first, then apply using your standard rolling upgrade procedures. No configuration changes or special migration steps are required.

• enhancementUpdate container image tags in deployments

  Update your deployment manifests, Helm charts, and CI/CD pipelines to reference the new v1.34.5 container images. This is particularly important for clusters using specific version tags rather than floating tags to ensure you receive the latest stability fixes.