Skip to content
Get started (free)

Container images for SDP 26.7

Every image an SDP release ships: copy a registry reference, follow one to its bill of materials, or prepare a deterministic air-gap mirror.

SDP 26.7 shipped 2026-07-21. Data indexed 2026-11-20 13:36 UTC.

Registry

63 images on OCI

126 platform images (amd64, arm64) 126 with SBOM 78.1 GiB for all platforms

Mirror one complete release

Copy every image in SDP 26.7 into your own registry, one command per image. Digest-pinned sources keep the inventory immutable, and tagged destinations stay usable by SDP.

Take the image list

Feed these references to your own mirroring tool or CI. Digests are immutable, and tags follow the release.

Generate a mirror script

Enter a registry host and optional path. A trailing slash is removed.

Needs oras and cosign: oras copy -r for images built from 25.11, cosign copy for older images and the CSI sidecars.

126 platform images, about 78.1 GiB (amd64 39.1 GiB, arm64 38.9 GiB). Every platform is copied, so the image index, its signature and its digests stay valid.

Preview of mirror-sdp-26.7.sh
Enter a valid target repository prefix to generate one copy command for each of the 63 images in SDP 26.7.

Point SDP at your mirror

Both the product resources and the operators pull images, so point each at your mirror. Image names and tags stay the same, only the source registry changes.

Product resources

Add the highlighted lines to every product resource, shown here on an Airflow example. repo points image pulls at your mirror, and pinning stackableVersion to the release you mirrored keeps the tag exact, since offline there is nothing to fall back to. See Product image selection.

apiVersion: airflow.stackable.tech/v1alpha1
kind: AirflowCluster
metadata:
name: my-airflow
spec:
image:
productVersion: 3.0.6
stackableVersion: 26.7.0
repo: <prefix>

Operators (Helm)

Operators install with Helm, so each chart gets its image repository as a value. The tag follows the chart version. From 26.7 the charts take only the registry prefix and add the image name themselves. secret-operator and listener-operator look for their CSI sidecars under <prefix>/sig-storage/, so the mirror has to keep that path, as the script above does. See Running Stackable in an air-gapped environment.

helm install for the 16 operators of SDP 26.7
helm install airflow-operator oci://oci.stackable.tech/sdp-charts/airflow-operator --version 26.7.0 \
  --set image.repository='<prefix>'
helm install druid-operator oci://oci.stackable.tech/sdp-charts/druid-operator --version 26.7.0 \
  --set image.repository='<prefix>'
helm install hdfs-operator oci://oci.stackable.tech/sdp-charts/hdfs-operator --version 26.7.0 \
  --set image.repository='<prefix>'
helm install hbase-operator oci://oci.stackable.tech/sdp-charts/hbase-operator --version 26.7.0 \
  --set image.repository='<prefix>'
helm install hive-operator oci://oci.stackable.tech/sdp-charts/hive-operator --version 26.7.0 \
  --set image.repository='<prefix>'
helm install kafka-operator oci://oci.stackable.tech/sdp-charts/kafka-operator --version 26.7.0 \
  --set image.repository='<prefix>'
helm install nifi-operator oci://oci.stackable.tech/sdp-charts/nifi-operator --version 26.7.0 \
  --set image.repository='<prefix>'
helm install spark-k8s-operator oci://oci.stackable.tech/sdp-charts/spark-k8s-operator --version 26.7.0 \
  --set image.repository='<prefix>'
helm install superset-operator oci://oci.stackable.tech/sdp-charts/superset-operator --version 26.7.0 \
  --set image.repository='<prefix>'
helm install zookeeper-operator oci://oci.stackable.tech/sdp-charts/zookeeper-operator --version 26.7.0 \
  --set image.repository='<prefix>'
helm install opa-operator oci://oci.stackable.tech/sdp-charts/opa-operator --version 26.7.0 \
  --set image.repository='<prefix>'
helm install opensearch-operator oci://oci.stackable.tech/sdp-charts/opensearch-operator --version 26.7.0 \
  --set image.repository='<prefix>'
helm install commons-operator oci://oci.stackable.tech/sdp-charts/commons-operator --version 26.7.0 \
  --set image.repository='<prefix>'
helm install listener-operator oci://oci.stackable.tech/sdp-charts/listener-operator --version 26.7.0 \
  --set image.repository='<prefix>'
helm install secret-operator oci://oci.stackable.tech/sdp-charts/secret-operator --version 26.7.0 \
  --set image.repository='<prefix>'
helm install trino-operator oci://oci.stackable.tech/sdp-charts/trino-operator --version 26.7.0 \
  --set image.repository='<prefix>'

Other formats

The same images for other tools. skopeo sync gives the mirror the same layout as the copy script. On OpenShift, image mirror sets make the cluster pull from <prefix> without changing an image name in Helm values or Stacklets. They match the layout of the copy script and skopeo sync. oc-mirror keeps the source path instead and writes its own mirror sets into its workspace.

cat > sync-sdp-26.7.yaml <<'EOF' oci.stackable.tech: images: sdp/airflow: - "2.9.3-stackable26.7.0" - "3.0.6-stackable26.7.0" - "3.1.6-stackable26.7.0" - "3.2.2-stackable26.7.0" sdp/airflow-operator: - "26.7.0" sdp/druid: - "30.0.1-stackable26.7.0" - "35.0.1-stackable26.7.0" - "37.0.0-stackable26.7.0" sdp/druid-operator: - "26.7.0" sdp/hadoop: - "3.3.6-stackable26.7.0" - "3.4.2-stackable26.7.0" - "3.4.3-stackable26.7.0" - "3.5.0-stackable26.7.0" sdp/hdfs-operator: - "26.7.0" sdp/hbase: - "2.6.4-stackable26.7.0" - "2.6.6-stackable26.7.0" sdp/hbase-operator: - "26.7.0" sdp/hive: - "3.1.3-stackable26.7.0" - "4.0.0-stackable26.7.0" - "4.0.1-stackable26.7.0" - "4.2.0-stackable26.7.0" sdp/hive-operator: - "26.7.0" sdp/kafka: - "3.9.1-stackable26.7.0" - "3.9.2-stackable26.7.0" - "4.1.1-stackable26.7.0" - "4.2.1-stackable26.7.0" sdp/kafka-operator: - "26.7.0" sdp/nifi: - "2.6.0-stackable26.7.0" - "2.7.2-stackable26.7.0" - "2.9.0-stackable26.7.0" sdp/nifi-operator: - "26.7.0" sdp/omid: - "1.1.2-stackable26.7.0" - "1.1.3-stackable26.7.0" sdp/spark-k8s: - "3.5.8-stackable26.7.0" - "4.1.1-stackable26.7.0" - "4.1.2-stackable26.7.0" sdp/spark-k8s-operator: - "26.7.0" sdp/superset: - "4.1.4-stackable26.7.0" - "6.0.0-stackable26.7.0" - "6.1.0-stackable26.7.0" sdp/superset-operator: - "26.7.0" sdp/zookeeper: - "3.9.4-stackable26.7.0" - "3.9.5-stackable26.7.0" sdp/zookeeper-operator: - "26.7.0" sdp/opa: - "1.12.3-stackable26.7.0" - "1.16.2-stackable26.7.0" sdp/opa-operator: - "26.7.0" sdp/opensearch: - "3.1.0-stackable26.7.0" - "3.4.0-stackable26.7.0" - "3.6.0-stackable26.7.0" sdp/opensearch-dashboards: - "3.1.0-stackable26.7.0" - "3.4.0-stackable26.7.0" - "3.6.0-stackable26.7.0" sdp/opensearch-operator: - "26.7.0" sdp/commons-operator: - "26.7.0" sdp/listener-operator: - "26.7.0" sdp/secret-operator: - "26.7.0" sdp/trino: - "477-stackable26.7.0" - "479-stackable26.7.0" - "481-stackable26.7.0" sdp/trino-operator: - "26.7.0" EOF skopeo sync --all --src yaml --dest docker sync-sdp-26.7.yaml <prefix> cat > sync-sdp-26.7-sig-storage.yaml <<'EOF' oci.stackable.tech: images: sdp/sig-storage/csi-node-driver-registrar: - "v2.15.0" sdp/sig-storage/csi-provisioner: - "v5.3.0" EOF skopeo sync --all --src yaml --dest docker sync-sdp-26.7-sig-storage.yaml <prefix>/sig-storage

Admit only signed images

With the signatures in the mirror, an admission controller can refuse any image under <prefix> that a Stackable release workflow did not sign. Both examples list the workflows that sign released images: the product and operator builds at a release tag, and the mirror workflow for upstream images such as the CSI sidecars. Development builds do not match. The controller needs to reach Sigstore, or its own offline trust configuration. How to install and configure the controller: enabling verification of image signatures.

apiVersion: kyverno.io/v1 kind: ClusterPolicy metadata: name: verify-stackable-images spec: webhookTimeoutSeconds: 30 rules: - name: stackable-signature match: any: - resources: kinds: - Pod verifyImages: - imageReferences: - "<prefix>/*" failureAction: Enforce mutateDigest: false attestors: - count: 1 entries: # product image built by a docker-images release workflow at a release tag - keyless: subjectRegExp: "^https://github\\.com/stackabletech/docker-images/\\.github/workflows/(reusable_build_image\\.yaml|release\\.yml|build_[a-z0-9-]+\\.yaml)@refs/tags/[1-9][0-9]*\\.[0-9]+\\.[0-9]+$" issuer: "https://token.actions.githubusercontent.com" # operator image built by its own repository at a release tag - keyless: subjectRegExp: "^https://github\\.com/stackabletech/[a-z0-9-]+-operator/\\.github/workflows/build\\.ya?ml@refs/tags/[1-9][0-9]*\\.[0-9]+\\.[0-9]+$" issuer: "https://token.actions.githubusercontent.com" # upstream image copied by the docker-images mirror workflow - keyless: subjectRegExp: "^https://github\\.com/stackabletech/docker-images/\\.github/workflows/mirror\\.yaml@refs/heads/main$" issuer: "https://token.actions.githubusercontent.com"