Simplifying Blueprint and Add-on Management with Draft Versions
Managing infrastructure at scale demands both agility and precision—especially when it comes to version control. At Rafay, we have long supported versioning for key configuration objects such as Blueprints and Add-ons, enabling platform teams to roll out changes systematically and maintain operational consistency.
However, as many teams have discovered, managing these versions during testing and validation phases can introduce unnecessary complexity. We are excited to announce a major usability enhancement: Support for Draft Versions.
Why Versioning Matters
Versioning in Rafay’s platform delivers several key advantages:
- Change Tracking: Keep a historical record of changes made to Blueprints and Add-ons over time
- Staged Rollouts: Gradually deploy updates across environments and clusters to minimize risk
- Compliance Assurance: Demonstrate adherence to organizational policies and track Day-2 changes in a controlled way
These capabilities are especially crucial for teams responsible for maintaining secure, production-grade Kubernetes environments
The Challenge: Version Sprawl During Testing
While versioning is powerful, it has traditionally introduced friction during the testing and validation phase. Each time a platform engineer made a minor change to an Add-on or Blueprint, a new version needed to be created—even if the version wasn’t production-ready.
This led to:
- Version fatigue, with large volumes of partially validated versions cluttering the system
- Increased manual overhead and inefficiency for platform teams
- Risk of accidental usage of incomplete configurations in downstream projects
