> For the complete documentation index, see [llms.txt](https://docs.platform9.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.platform9.com/self-managed-cloud-platform/lts3-release-notes.md). # LTS3 Release Notes ### 5.14 * Continuous backup is now supported via cronjobs * Introduced `airctl` commands to provide `etcd` backup and restore features * Workload cluster support for Kubernetes 1.32 and 1.33 * Updated the management cluster to Kubernetes 1.33 ### 5.12 * Highly-available management plane running PMK 5.12 * Support for workload clusters with K8s 1.29, 1,30 and 1.**31** * Management plane monitoring, management cluster image pinning to prevent GC ### 5.11 / LTS5 * Highly-available management plane running PMK 5.11 * Underlying management cluster upgraded to K8s 1.**30** * Support for workload clusters with K8s 1.28, 1.29 and 1.**30** * Management plane monitoring, management cluster image pinning to prevent GC ### 5.10 / LTS4 * Highly-available management plane running PMK 5.10 * Underlying management cluster upgraded to K8s 1.**27** * Support for Ubuntu OS (Ubuntu 22.04 LTS) * Support for workload clusters with K8s 1.27, 1.28 and 1.29 ### 5.9 / LTS3 (GA) * Highly-available management plane running PMK 5.9 * Underlying management cluster upgraded to K8s 1.25 * Support for running the management plane and workload clusters in "connected" mode - with access to the internet * Support for workload clusters with K8s 1.24 and 1.25 ### 5.6 / LTS2 * Highly-available management plane running PMK 5.6. The management plane now runs as containers on an underlying management cluster running K8s 1.21 * Support for workload clusters with K8s 1.21, 1.22, and 1.23 * Docker support deprecated. Switched to running user workloads on a containerd runtime * Management plane and workload clusters are designed to work in air-gapped environments only ### 5.3 / LTS1 * Single node management plane running PMK 5.3 * Support for workload clusters with K8s 1.20 * Users workloads running on a Docker runtime * Management plane and workload clusters are designed to work in air-gapped environments only ### Release Notes [5.14 Release](https://pf9.developerhub.io/kubernetes-docs/PEC/smcp-514-release-notes) [5.12 Release](https://pf9.developerhub.io/kubernetes-docs/5.12/PEC/smcp-5-12-release-notes) [5.11 Release](https://pf9.developerhub.io/kubernetes-docs/5.11/PEC/smcp-5-11-release-notes) [5.10 (LTS4) Release](https://pf9.developerhub.io/kubernetes-docs/5.10/PEC/pec-release-notes#510--lts4) [LTS3 (GA) Release](https://pf9.developerhub.io/kubernetes-docs/v5.9/PEC/lts3-release-notes) [LTS2 Release](https://pf9.developerhub.io/kubernetes-docs/v5.7/PEC/pec-lts2-release) * [LTS2 Patch 1 Release](https://pf9.developerhub.io/kubernetes-docs/v5.7/PEC/pec-lts2-release#2022-22-12-platform9-edge-cloud-lts2-patch-1) * [LTS2 Patch 2 Release](https://pf9.developerhub.io/kubernetes-docs/v5.7/PEC/pec-lts2-release#platform9-edge-cloud-lts-2-patch-2) * [LTS2 Patch 3 Release](https://pf9.developerhub.io/kubernetes-docs/v5.7/PEC/pec-lts2-release#platform9-edge-cloud-lts-2-patch-3) * [LTS2 Patch 4 Release](https://pf9.developerhub.io/kubernetes-docs/v5.7/PEC/pec-lts2-release#platform9-edge-cloud-lts-2-patch-4) --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.platform9.com/self-managed-cloud-platform/lts3-release-notes.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.