Skip to main content

Integrate SKE with Backstage

Publish your Promises in Backstage so developers can discover, request and manage resources.

The integration has two directions:

The Portal Controller generates catalog files. Backstage reads them; it does not receive them through its API. The two SKE plugin packages provide request actions and resource pages.

Set up the integration​

  1. Generate Backstage entities. Install or reuse the controller, choose catalog storage, label a Promise and verify its files.
  2. Configure Backstage. Install the plugins and configure discovery. Verify the Promise Component and its Template.
  3. Send resource requests to Kratix. Configure transport, approval and namespaces. Create, update and delete a resource.

Catalog storage and request storage are separate choices. Git-based requests need a GitOps agent to apply them to the platform.

Customise your integration​

Existing Backstage Controller installation

Follow the migration guide instead of creating a second integration.

For local plugin development, you can use the development image. To generate entities directly from Promise workflows without deploying the controller, see Run the adapter as a pipeline stage.

Next steps​

Start with Generate Backstage entities.