This guide walks you through the prerequisites and step-by-step configuration of a Fleet Environment Template to perform bulk updates across multiple environments using the Template Catalog.
Before starting, ensure the following are available:
API Key
Must belong to a user with sufficient RBAC permissions to modify environments across the targeted projects or organization.
Controller Endpoint
Typically console.rafay.dev. This targets the correct Rafay Controller environment.
Access to the Template Catalog
Ensure the Fleet Environment Template is available within your system template catalog and that you have permission to use it.
The Fleet Template enables centralized, bulk configuration updates across environments based on:
- Project filters
- Environment labels
- Template name and version
- Input variable changes
This is ideal for day-2 operations such as:
- Kubernetes version upgrades
- Blueprint updates
- AMI updates
The Fleet Environment Template provides a scalable, centralized way to update environment configurations across projects—ideal for Day-2 operations such as Kubernetes version upgrades, blueprint updates, and AMI rollouts.
By launching the template from a shared central project, platform teams ensure consistency, reduce operational overhead, and eliminate manual effort.