Skip to main content

Air-Gapped Installation

Deprecated

The standalone Backstage Controller is deprecated. It continues to work, see Migrating from the Backstage Controller when you are ready to move.

This page covers how to install the Backstage Controller in air-gapped or network-restricted environments. For the SKE Backstage plugins, see Air-Gapped Plugin Installation.

SKE Backstage Controller​

In air-gapped environments, you must mirror the Backstage Controller image and deployment manifests into your own infrastructure before installing. Once mirrored, follow the standard Installing the Backstage Controller steps.

Mirror the Backstage Controller image​

Mirror the following image using the same version that you set on the Backstage integration:

ghcr.io/syntasso/backstage-controller:<BACKSTAGE_CONTROLLER_VERSION>

This single image contains both the Backstage Controller and the Backstage Generator used by its Workflow Jobs. You do not need to mirror a separate generator image.

The Backstage Controller uses the registry configured by imageRegistry.host in the SKE Operator Helm chart. If you change the image path in your internal registry, set imageRegistry.backstageControllerImage.name to the new path.

Mirror the Backstage Controller release manifests​

Like the SKE distribution, you will need to ensure that the Backstage Controller deployment manifests are available in the SKE Release Storage, the S3-compatible bucket or Git repository that is accessible from the Platform Cluster.

You need to ensure that the manifests are downloaded to the SKE Release Storage and that the directory structure matches the Syntasso Enterprise Releases page. For instance:

ske
  v0.43.0
    ske-distribution.yaml
    release-metadata.json

backstage-controller
  v0.2.2
    backstage-controller.yaml