> 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/2026.4/upgrade/upgrade.md).

# Upgrade Overview

This section covers upgrading a <code class="expression">space.vars.product\_name</code> environment — preparing your hosts, sequencing the upgrade safely, and verifying that every service is healthy afterward.

<code class="expression">space.vars.product\_name</code> supports two deployment models:

* **SaaS** — Platform9 hosts and operates the management plane.
* **Self-Hosted** — you operate the management plane on-premise.

The runbooks below apply to both models. Steps that are specific to the on-premise (Self-Hosted) management plane — primarily the `airctl` commands — are called out separately within each runbook.

## In this section

* [Host Upgrade Runbook](/private-cloud-director/2026.4/upgrade/host-upgrade-runbook.md) — pre-upgrade environment checks, host upgrade ordering across multi-role hosts, Ubuntu 22.04-to-24.04 OS upgrade caveats, and failure recovery.
* [Post-Upgrade Verification](/private-cloud-director/2026.4/upgrade/post-upgrade-verification.md) — the checklist to confirm region health, host roles, GPU, storage, and networking are healthy, then re-enable VM HA and DRR.

## Related pages

* **Self-Hosted management plane upgrade:** [Upgrade Management Plane and Hosts](/private-cloud-director/2026.4/getting-started/self-hosted/upgrade.md) covers upgrading an on-premise (Self-Hosted) deployment with `airctl`.


---

# 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/2026.4/upgrade/upgrade.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.