In general, Astro Private Cloud (APC) will support a given version of Kubernetes through its End of Life. This includes Kubernetes upstream and cloud-managed variants like GKE, AKS, and EKS. When a version of Kubernetes reaches End of Life, support will be removed in the next major or minor release of APC. For more information on Kubernetes versioning and release policies, refer to Kubernetes Release History or your cloud provider.
See the following table for all supported Kubernetes versions in each maintained version of APC.
If there are no workloads running on the nodes you want to upgrade, there won’t be an immediate impact on the Astronomer or Airflow components during the initial phase of upgrading your Kubernetes node pools. To minimize disruptions, however, perform a controlled rollout restart of the worker nodes. During your controlled rollout, monitor the health of the new nodes and workloads before decommissioning the old nodes.
Before beginning the upgrade process, ensure you have all necessary backups ready. After upgrading, verify that all Astro Private Cloud and Airflow components are running as expected on the new nodes. Once your Kubernetes cluster has been upgraded to a version that is compatible with your Astro Private Cloud version, you do not need to change your Astro Private Cloud configurations or settings. However, the upgrade requires restarting the Kubelet on each node, which causes the Astro and Airflow components to also restart.
For more information on upgrading Kubernetes versions, follow the guidelines offered by your cloud provider.