> ## 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 Templates

> Reusable, agentic upgrade workflows for 100s of Cloud Native Projects and clusters.

## What are Chkk Upgrade Templates?

Chkk Upgrade Templates are **agentic, reusable workflows** that serve as standardized blueprints for safely upgrading clusters, Cloud Native Projects, application services, and operators. They represent the foundation of Chkk's upgrade management system.

### Key Characteristics

**1. Agentic Workflows**

* Templates are generated using AI to create tested sequences of steps and stages
* They incorporate best practices and proven upgrade methodologies
* Each template is tailored to specific components (clusters, Projects, operators, etc.)

**2. Reusable Blueprints**

* Templates are environment-scoped rather than cluster-specific
* A single template can be used to create multiple Upgrade Plans for different clusters
* They provide consistent upgrade processes across multiple environments

**3. Comprehensive Coverage**

* **Cluster Upgrade Templates**: For upgrading entire clusters
* **Project Upgrade Templates**: For upgrading specific Cloud Native Projects, application services, and operators
* Support for both **In-Place** and **Blue-Green** upgrade strategies

**4. Customizable and Reviewable**

* Teams can review templates before approval
* Custom steps can be added to align with organizational guidelines
* Internal change-management standards can be applied
* Teams can confirm which versions to upgrade now versus later

### Template Lifecycle

1. **Waiting for Template** → Template is being generated
2. **Available** → Template is ready for review and customization
3. **Approved** for Use → Template has been reviewed, customized, and officially approved
4. **Environment Upgraded** → Template has been used successfully

### Key Features

**1. Approval Process**

* Templates must be explicitly approved before use
* Chkk logs who approved each template for team visibility
* Approval includes the ability to add comments and custom steps

**2. Standardization Benefits**

* Reduces context switching between different upgrade processes
* Preserves knowledge by codifying best practices
* Promotes reuse of best practices across the organization
* Enables consistent workflows organization-wide

**3. Integration Support**

* Templates work with various deployment methods (Helm, Kustomize, YAML manifests)
* Support for private registries and custom images
* Compatible with GitOps and CI/CD workflows

### How Templates Work

* **Generation**: Templates are created either through direct requests or derived from Upgrade Assessments
* **Review & Customization**: Teams review the template, add custom steps, and adjust to organizational needs
* **Approval**: Templates are marked as "Approved for Use" with proper logging
* **Instantiation**: Approved templates are used to create cluster-specific Upgrade Plans
* **Reuse**: The same template can be instantiated multiple times for different clusters

### Benefits

* **Faster Upgrades**: Pre-tested workflows eliminate guesswork
* **Consistent Processes**: Standardized approaches across multiple clusters
* **Reduced Risk**: Proven methodologies minimize upgrade failures
* **Knowledge Preservation**: Best practices are captured and reused
* **Team Collaboration**: Clear approval processes and delegation support

Upgrade Templates essentially serve as the "recipes" that teams can customize and approve once, then use repeatedly to create specific "cooking instructions" ([Upgrade Plans](/product/upgrade-copilot/plans)) for individual clusters.

### Integration with Chkk Upgrade Copilot

Upgrade Templates 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** → Provide detailed, pre-verified workflows
3. [Upgrade Plans](/product/upgrade-copilot/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.
