> ## Documentation Index
> Fetch the complete documentation index at: https://docs.chkk.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Upgrade Plans

> Cluster-specific or Project-specific upgrade workflows instantiated from approved Templates.

## What are Chkk Upgrade Plans?

Chkk Upgrade Plans are instantiated, **cluster-specific workflows** that provide detailed, step-by-step instructions for safely upgrading individual clusters, Cloud Native Projects, application services, and operators. They are created from approved [Upgrade Templates](/product/upgrade-copilot/templates) and represent the execution phase of Chkk's upgrade process.

### Key Characteristics

**1. Instantiation from Templates**

Upgrade Plans are created by instantiating an approved [Upgrade Template](/product/upgrade-copilot/templates) for a specific cluster. They inherit all the information from the template plus additional cluster-specific details like:

* The cluster's name and region
* Node Group details
* Which applications are using **deprecated/removed APIs**
* **Application client changes** in running Cloud Native Projects
* **Application misconfigurations** (like incorrect Pod Disruption Budgets) that could cause upgrades to fail

**2. Types of Upgrade Plans**

* **Cluster Upgrade Plans**: For upgrading entire clusters
* **Project Upgrade Plans**: For upgrading specific Cloud Native Projects, application services, or operators within a cluster

**3. Lifecycle Statuses**

Upgrade Plans move through these statuses:

* **Waiting for Plan**: Being generated
* **In Progress**: Ready for execution
* **Completed**: Cluster upgraded successfully
* **Canceled**: User-initiated cancellation

**4. Key Features**

* **Standardized Workflows**: Ensure consistent upgrade processes across multiple clusters
* **Delegation Support**: Allow senior engineers to assign upgrade tasks to team members with confidence
* **Progress Tracking**: Monitor overall progress through distinct stages
* **Customization**: Can be tailored for specific clusters even after instantiation
* **Reusability**: Based on proven templates that can be used across multiple environments

### How They Work

1. **Creation**: Generated from approved Upgrade Templates through the instantiation process
2. **Customization**: Include cluster-specific information and can be further customized with additional steps
3. **Execution**: Provide a structured, step-by-step approach to performing upgrades
4. **Tracking**: Allow teams to monitor progress and mark completion
5. **Collaboration**: Support team coordination through features like comments and activity feeds

### Integration with Chkk Upgrade Copilot

Upgrade Plans are one of the three complementary capabilities of Chkk Upgrade Copilot:

1. [Upgrade Assessments](/product/upgrade-copilot/assessments) → Map scope, impact, and dependencies
2. [Upgrade Templates](/product/upgrade-copilot/templates) → Provide detailed, pre-verified workflows
3. **Upgrade Plans** → Instantiate templates for specific cluster execution

<Note>
  Upgrade Templates/Plans are preverified against a [Digital Twin](/resources/glossary/#digital-twin) of your running configuration and take longer to generate; use them closer to execution.
</Note>

This comprehensive approach ensures teams can scope effort and delegate work early, making upgrades faster, safer, and more predictable.