Kubernetes Project Lifecycle

eLxr Kubernetes

The Cloud Native Computing Foundation (CNCF), which governs Kubernetes, defines the lifecycle used by the upstream open-source project, k3s and eLxr Kubernetes.

• eLxr Kubernetes encompass a suite of Kubernetes software and utilities packaged for easy deployment and management on any supported eLxr release.

• eLxr Kubernetes packages include the three latest supported versions and offers a choice between two CNCF K8s distributions.

  • Kubernetes, aka Vanilla K8s, is identical to upstream releases, packaged with no modifications.

  • K3S is a highly optimized lightweight alternative with very low resource requirements.

• Kubernetes software that is distributed in eLxr inherits the upstream project lifecycle and release cadence independently from the eLxr project

• Kubernetes software included in eLxr releases will not be covered under the standard eLx Support Lifecycle.

• eLxr Kubernetes packages will be added after each minor release, updated after patch releases, and removed at end of life.

Versioning & Support Policy

Kubernetes versions use Semantic Versioning terminology.

• Major.Minor.Version format: vX.Y.Z (for example v1.28.3).

  • Major (X): Rarely released; introduces significant changes.

  • Minor (Y): Added functionality and changes in behavior are backward-compatible .

  • Patch (Z): Backward compatible security fixes and bug fixes.

• Kubernetes follows an N-2 support policy (meaning that the three most recent minor versions receive security and bug fixes)

• Kubernetes release cadence follows a 15 week minor release cycle, with 2 weeks between release cycles

  • Release cadence is softly targeted and can be influenced by critical security issues, major bugs, and events/holidays.

  • patch releases (x.y.Z): monthly but often faster.

  • minor releases (x.Y.z): every four months.

• Long-term support (LTS)

  • The project is not currently in a place that can provide long-term support releases.

Support Timeline for Minor Versions

Kubernetes releases currently happen approximately three times per year.

• Minor releases are supported after the release for approximately 14 months.

  • Standard period has an active patch release series of 12 months

  • Upgrade period where the patch release series enters maintenance mode for the final two months.

    • Critical security patches

    • Upgrade blocking fixes

    • Dependency issues

  • Security maintenance is only provided for actively supported minor versions.

End-of-Life (EOL) Policy

• Target date is 14 months after initial release.

• eLxr removes removes packages from repositories that reach EOL

• Kubernetes removes old minor versions from support in a rolling cadence.

• No backports or security fixes after EOL