> 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/private-cloud-director/getting-started/host-operating-system-support-matrix.md).

# Host Operating System Support Matrix

This page describes which host operating systems are supported for each Private Cloud Director release, along with deprecation timelines and end-of-support dates.

| PCD Release      | Ubuntu 22.04   | Ubuntu 24.04 | Platform9 OS powered by Rocky Linux from CIQ (RLC) 10.2 |
| ---------------- | -------------- | ------------ | ------------------------------------------------------- |
| **January 2026** | Supported      | Supported    | --                                                      |
| **April 2026**   | Supported      | Supported    | --                                                      |
| **August 2026**  | Deprecated     | Supported    | Supported                                               |
| **October 2026** | Deprecated     | Supported    | Supported                                               |
| **January 2027** | Deprecated     | Supported    | Supported                                               |
| **April 2027**   | End of support | Supported    | Supported                                               |

**Legend:**

* Supported = fully tested and maintained
* Deprecated = still functional, but no longer recommended for new deployments; plan to migrate
* End of support = no longer tested, patched, or supported

{% hint style="info" %}
**Ubuntu Support**

Ubuntu host operating systems follow a bring-your-own-OS model. You provide, install, and maintain Ubuntu yourself, and Platform9 supports Private Cloud Director on the Ubuntu versions marked Supported in the table above. Platform9 does not package, harden, or manage the Ubuntu operating system, and there is no Platform9-delivered Ubuntu image equivalent to Platform9 OS.
{% endhint %}

{% hint style="info" %}
**Rocky Linux Support**

Private Cloud Director is supported only on Platform9 OS powered by Rocky Linux from CIQ (RLC) 10.2 and installed through the Platform9 OS ISO. Platform9 OS is a controlled, hardened configuration: it is hardened to the CIS Level 1 benchmark and is configured to pull packages and updates only from the Platform9 validated package repository. Enabling a third-party package repository on a Platform9 OS host is not a supported production configuration. Platform9 builds, tests, patches, and supports this operating system together with PCD as a single integrated stack.

Community Rocky Linux is not a supported PCD host operating system. This applies regardless of the version number: a host running community Rocky Linux 10.2 is still unsupported, because it does not carry the Platform9 OS hardening and does not use the Platform9 validated package repository, so it is not the configuration PCD is built and tested against. Private Cloud Director installed on a customer-provided Rocky Linux host is an unsupported configuration.
{% endhint %}

### Important dates

**August 2026:** Ubuntu 22.04 is deprecated. New cluster deployments should use Ubuntu 24.04 or Platform9 OS powered by Rocky Linux 10.2.

**January 2027:** Last PCD release that includes Ubuntu 22.04 support.

**April 2027:** Ubuntu 22.04 reaches end of support. Hosts running Ubuntu 22.04 must be migrated before upgrading to this release.

### Migration between host operating systems

Workload migration support depends on whether the source and destination hosts run the same host operating system.

| Migration type | Between Ubuntu and Platform9 OS hosts | Between Platform9 OS hosts |
| -------------- | ------------------------------------- | -------------------------- |
| Live migration | Not supported                         | Supported                  |
| Cold migration | Supported                             | Supported                  |

For details on migrating workloads from Ubuntu hosts to Platform9 OS hosts, see [Cross-OS Cold Migration: Ubuntu Hosts to Platform9 OS Hosts](/private-cloud-director/virtualized-clusters/virtualmachine/vm-migration.md#cross-os-cold-migration-ubuntu-hosts-to-platform9-os-hosts).

{% hint style="warning" %}
**Avoid mixed-OS clusters**

Running Ubuntu and Platform9 OS (Rocky) hosts together in the same virtualized cluster is not recommended, except when you are intentionally transitioning the cluster from Ubuntu to Platform9 OS. Live migration and VM evacuation do not work across operating system families, and mixing them in one cluster also affects Virtual Machine High Availability (VM HA) and Dynamic Resource Rebalancing (DRR). For details, see [Live Migration Across Operating System Families](/private-cloud-director/virtualized-clusters/virtualmachine/vm-migration.md#live-migration-across-operating-system-families).
{% endhint %}


---

# 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/private-cloud-director/getting-started/host-operating-system-support-matrix.md?ask=<question>&goal=<user_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.
