Downloads

Kubernetes Edge Supported Platforms

This page lists which Kubernetes platform and versions the Kubernetes edge can run on, and which of them Ataccama has validated. The table columns mean the following:

  • Supported versions: Ataccama accepts support tickets and fixes bugs on these versions.

  • Validated on: Ataccama has verified installation and end-to-end job execution on this version.

Supported platforms

The Kubernetes edge supports Azure Kubernetes Service (AKS) only.

Platform Supported versions Validated on

AKS

1.31, 1.32, 1.33, 1.34, 1.35, and 1.36.

Chart 1.0.0-saas-edge on AKS 1.36, October 2, 2026.

The supported versions reflect the state as of October 1, 2026. On that date, AKS offers 1.34, 1.35, and 1.36 in standard support, and 1.31, 1.32, and 1.33 only in AKS long-term support (LTS). Any patch release within a supported minor version is also supported.

Other Kubernetes platforms are not supported, including Amazon Elastic Kubernetes Service (EKS), Red Hat OpenShift, Google Kubernetes Engine (GKE), and self-managed upstream Kubernetes.

Cluster and tooling requirements

Your cluster needs the following:

  • Helm 3.8 or later: The chart is distributed from an Open Container Initiative (OCI) registry, which Helm supports from version 3.8.

  • Outbound connectivity: Access to the Ataccama Edge gateway, your tenant’s identity provider, Microsoft Entra ID, Azure Blob Storage, the Ataccama image registry, and Azure Key Vault if you use it. For the full list, see Kubernetes Edge Network Access Requirements. No inbound access is needed. For the Azure resources, see Prepare Azure Resources for Kubernetes Edge.

The following settings are recommended for any cluster that runs the edge:

  • A Container Network Interface (CNI) plugin that enforces NetworkPolicy, so you can restrict the edge namespace with your own policies.

  • Admission control, etcd encryption, and resource quotas.

Next steps

Was this page useful?