Skip to main content

Version management overview

FPT Cloud releases and updates Kubernetes versions according to Kubernetes Open Source Software (OSS) community standards.

  • The Kubernetes version format is x.y.z: x is the major version (incremented from x.y to x+1.y); y is the minor version (deprecated APIs are removed with each new minor version, incremented from 1.y to 1.y+1 — for example, 1.25 follows 1.24); z is the patch release, delivering bug fixes and security patches for a minor version.

  • FPT Cloud supports the 4 most stable Kubernetes minor versions at any time. The highest of the 4 is the default version. These versions are thoroughly tested and ready for production. Older versions are labeled deprecated until the end-of-life date published in the release notes.

  • FPT Cloud also supports newer community versions tagged Beta, still being refined through internal testing and user feedback. Once ready for production, a Beta version is promoted to Stable or GA (Generally Available).

  • Versions past end of standard support (by both the Kubernetes community and FPT Cloud) no longer receive technical support — no new Kubernetes fixes, no new cloud-provider capabilities, and no security patches.

    warning

    FPT Cloud does not guarantee SLA for end-of-life versions.

  • Kubernetes versions for standard clusters may differ from GPU clusters — a GPU cluster's default version is typically one minor version lower than a standard cluster's.

  • Worker Node OS images run on Ubuntu. Depending on the cluster's Kubernetes version, you can choose Ubuntu 22.04 or Ubuntu 24.04, change a running Worker Group's OS version on the Portal, and enable Auto Patch OS Image to receive security patches automatically within the same version. See Change Worker Node Pool OS Image Version.

  • A version enters maintenance status 2 months before its end-of-support date, shown in the portal. Clusters on a version approaching end-of-life get an email 1 month in advance (once per day) to the VPC owner, so you can upgrade proactively or configure Auto Upgrade Version. Once you upgrade, the emails stop.

  • For clusters with Auto Upgrade Version configured, the VPC owner gets an email with the specific upgrade schedule 3 days before the automatic upgrade.