Supported versions and compatibility
SKE components are versioned independently. Choose versions using each component's release notes and your support agreement. The requirements below come from published release records; they are not a matrix of all integration-tested combinations.
Portal component requirements
| Component or capability | Declared requirement | Release record |
|---|---|---|
Portal Controller v0.6.1 with Operator management | Operator v0.34.0 or later; SKE v0.59.0 or later | Portal Controller |
| Backstage request namespace policy | Portal Controller v0.6.1 or later, backend v0.24.0 or later and frontend v0.22.0 or later | Portal Controller and Backstage plugins |
Backend v0.24.0 and frontend v0.22.0 | Release notes declare compatibility with Backstage v1.55.0 | Backstage plugins |
Portal Patch v0.8.2 | Independently versioned image; pin the recipe grammar version used by your customisation | Portal Patch |
The Operator manages installation through Kratix and SKEIntegration resources. Its Helm
chart version selects the Operator distribution; the SKE and integration versions remain
separate configuration choices. The Portal Controller can also be installed
without the Operator.
Plan an upgrade
SKE v0.59.0 changes Promise and resource status fields. Its release record requires Portal
Controller v0.4.2 or later, or deprecated Backstage Controller v0.11.1 or later, alongside
the SKE upgrade. Review the SKE release notes before changing either component.
- Record installed component and chart versions, configuration, enabled features and customisations. Review backup and restore before changing the platform.
- Read the release notes for every intervening release of each component being changed. Look for required companion versions, changes to defaults and migration instructions.
- Upgrade the Operator first when the target integration requires a newer Operator schema. Coordinate SKE and controller changes where their release notes require them together.
- Upgrade Backstage plugins before enabling controller settings that require new scaffolder actions. Keep Portal Patch pinned and review recipes when changing its image version.
- Follow the SKE upgrade procedure and the component's installation guide. Verify platform readiness and a representative request, including portal status, customisation and health checks where enabled.
Support boundaries
Confirm requirements for your chosen releases and environment with Syntasso when the release records do not answer them, including Kubernetes versions and support lifetime. Preview features follow the Preview policy.
Browse the release index for platform components, integrations and pipeline stages.
