Understanding RKE2 and K3s Version Suffixes: +rke2r1, +rke2r2, +rke2rZ and +k3s1, +k3s2, +k3sZ
This document (000021777) is provided subject to the disclaimer at the end of this document.
Environment
- RKE2 and K3s Kubernetes distributions.
Situation
Users often encounter version tags like v1.28.3+rke2r2 or v1.27.15+k3s2 and seek clarification on the meaning of the +rke2rZ and +k3sZ suffixes.
Resolution
These suffixes denote the RKE2 or K3s-specific release number within a given Kubernetes version.
...r1or...s1indicates the initial RKE2 or K3s release built upon that Kubernetes version.- Subsequent releases, such as
...r2,...s2, etc., signify further RKE2 or K3s updates within the same Kubernetes version.
Reasons for Multiple RKE2/K3s Releases per Kubernetes Version:
- Bug Fixes: Addressing bugs or security vulnerabilities discovered after the initial release.
- Enhancements: Introducing new RKE2/K3s features or improvements without requiring a Kubernetes version upgrade.
- Dependency Updates: Updating internal dependencies (e.g., containerd, CNI plugins) to compatible versions.
Considerations for Upgrades:
- When upgrading RKE2 or K3s, pay close attention to both the Kubernetes version and the RKE2/K3s release number. Upgrades like
v1.25.5+rke2r1tov1.25.5+rke2r2signify an RKE2 update within the same Kubernetes version. - Always consult the official release notes for detailed information on changes included in each release, including bug fixes, new features, and dependency updates. Example: http://docs.rke2.io/release-notes/v1.28.X#release-v1283rke2r2
Cause
The +rke2rZ and +k3sZ suffixes provide a mechanism to differentiate RKE2 and K3s-specific releases within a particular Kubernetes version, enabling the distribution of bug fixes, enhancements, and dependency updates without requiring full Kubernetes version upgrades.
Additional Information
- This versioning scheme allows for more granular control over RKE2 and K3s updates, providing users with the ability to selectively apply specific fixes or features.
- Understanding these suffixes is crucial for maintaining stable and secure RKE2 and K3s clusters.
- These suffixes are not part of the upstream kubernetes versioning.
Disclaimer
This Support Knowledgebase provides a valuable tool for SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented "AS IS" WITHOUT WARRANTY OF ANY KIND.
- Document ID:000021777
- Creation Date: 08-Apr-2025
- Modified Date:14-May-2025
-
- SUSE Rancher
For questions or concerns with the SUSE Knowledgebase please contact: tidfeedback[at]suse.com
