Skip to content

Compatibility

This page tracks the public compatibility matrix from the main XTrinode repository. Keep it aligned with xtrinode/go.mod, tools/go.mod, root Makefile pins, and Helm chart dependencies.

ComponentCurrent versionSource
Go toolchain1.26.3xtrinode/go.mod, tools/go.mod
Kubernetes API librariesv0.35.0xtrinode/go.mod
controller-runtimev0.22.4xtrinode/go.mod
controller-tools / controller-genv0.20.1tools/go.mod
KEDA Go modulev2.18.3xtrinode/go.mod
KEDA Helm chart2.18.0helm/xtrinode-operator/Chart.yaml
XTrinode Helm chart version0.1.0helm/xtrinode*/Chart.yaml version fields and umbrella dependencies
XTrinode component image version0.1.0helm/xtrinode*/Chart.yaml appVersion fields
Public release image architecturelinux/amd64.github/workflows/release.yml, DOCKER_PLATFORMS
Default Trino runtime image tag480Makefile TRINO_IMAGE_TAG, internal/config
Trino runtime compatibility targettrino-1.42.2 / app 480Upstream Trino chart reference and runtime image pin
golangci-lintv2.12.1tools/go.mod
Provider pathCurrent postureNotes
GCP / GKE / CAPGFully exercised cloud pathIncludes Terraform, deployment automation, CAPG bootstrap, managed nodepool smoke coverage, and KEDA/resume smoke coverage.
AWS / EKS / CAPAExperimental provider-validation pathTerraform, deploy scripts, API-server auth wiring, and unit-tested nodepool resource generation exist, but the path is not thoroughly live-smoke validated.
Azure / AKS / CAPZExperimental provider-validation pathTerraform, deploy scripts, API-server auth wiring, and unit-tested nodepool resource generation exist, but the path is not thoroughly live-smoke validated.
  • Do not bump Kubernetes libraries, controller-runtime, or controller-tools independently unless generated CRDs/manifests are regenerated and make ci-verify-manifests passes.
  • Keep the KEDA Go module and Helm chart versions intentionally reviewed together. They do not have to be byte-identical, but drift should be explained in the changing PR.
  • Keep all XTrinode chart version fields and umbrella dependency versions aligned with the XTrinode release version.
  • Keep all XTrinode chart appVersion fields aligned with the same XTrinode release version. Do not use the Trino runtime tag or upstream Trino chart version as the operator, API server, or gateway image or chart version.
  • Treat public image architecture support as release metadata. Update this page if release publishing changes from amd64-only to multi-platform images.
  • Treat Trino runtime image/chart drift as an explicit compatibility decision. Catalog property names and metrics exposed by Trino can change across Trino releases.
  • Update this page with release, dependency, and runtime pin changes.