Backstage Controller
Overview
The Backstage Controller generates Backstage components and templates for Promises and Resource Requests.
The release manifest is available at:
http://syntasso-enterprise-releases.s3-website.eu-west-2.amazonaws.com/#backstage-controller/
Release Notes
v0.4.0 (2025-10-07)
0.4.0 requires SKE 0.37.0 and above.
If you're running SKE with a lower version, please upgrade SKE first before upgrading to this version of Backstage Controller.
Released in Helm Chart version version 0.4.1
Features
- SKE backstage generator image is now part of the Backstage Controller image. If you are using the generator pipeline stage directly, please update your image reference to the Backstage Controller image.
v0.3.1 (2025-09-16)
Released in Helm Chart version version 0.3.0
Fixes
- This fixes a bug where the Backstage Controller would restart when a promise is was deleted
v0.3.0 (2025-08-26)
Features
- SKE backstage generator image used by the Backstage Controller can be customized to a registry of your choice. This can be used when deploying the controller in an air-gapped environment. For more details, refer to the installation guide.
v0.2.1 (2025-07-23)
v0.2.1 requires SKE 0.32.0 and above.
If you're running SKE with a lower version, please upgrade SKE first before upgrading to this version of Backstage Controller.
v0.2.0 (2025-07-16)
Features
- Introduce
entityGenerationOptionsto theBackstageEntityCustomizationresource. See Backstage Entity Customization for more details. - Promises must now declare the BackstageEntityCustomization they want to use
via the
kratix.io/backstage-customizationlabel. - Resources created with the label
kratix.io/backstageset to"false"won't be processed by the Backstage Controller. This allows users to exclude specific resources from having entities in Backstage, such as the resources created by Compound Promises.
v0.1.2 (2025-06-05)
Fix
syntasso-registrysecret, containing a token that can access the syntasso image registry, is required in namespaces that the backstage controller workflows run. This is so users' environments can pull the ske-backstage-generator image automatically instead of manually loading the image to their environment.
v0.1.1 (2025-05-28)
Features
- Initial release
