Skip to main content

Prerequisites

Before installing SKE, prepare your cluster and obtain your access tokens. If you don't have an SKE licence, request a trial or discuss pricing.

Installation prerequisites​

You need:

  • A Kubernetes platform cluster and permission to install CRDs, controllers and webhooks.
  • kubectl, and Helm if you choose the Helm installation method.
  • An SKE licence token supplied by Syntasso. See Get access below.
  • Access to the image registry and release storage, or mirrors for an air-gapped installation.
  • cert-manager, or custom certificates for SKE's webhooks.
  • A Git repository or S3-compatible bucket to store generated workloads for GitOps delivery. You'll configure a StateStore, Destination and, for Kubernetes workloads, a GitOps agent after installing SKE.

SKE and the Operator run in kratix-platform-system. Referenced registry, release-storage and TLS Secrets must be in that namespace.

Get access​

Syntasso supplies two tokens with your SKE licence. Existing customers can use their Syntasso support channels.

The registry token pulls container images; the releases token downloads private release assets. They are not interchangeable.

Syntasso registry token​

This is your SKE licence token. Use it as skeLicense in the Helm installation, or to create an image pull Secret. It pulls private images from ghcr.io/syntasso as syntasso-pkg and commonly starts with ghp_.

Keep credentials in your approved secret-management system. Avoid committing tokens or Helm values containing credentials to source control.

Enterprise releases token​

The Enterprise releases token provides access to private assets in syntasso/enterprise-releases. It commonly starts with github_pat_. Use it as GH_TOKEN when installing the Promise Testing CLI. Do not use it as skeLicense.

Optional components​

Next steps​

Install via the Operator's Helm chart or manifests.

For an existing installation, see Upgrade SKE.