From 78ec688eaf9d8506af08dc9585f04b882dc35619 Mon Sep 17 00:00:00 2001 From: "mintlify[bot]" <109931778+mintlify[bot]@users.noreply.github.com> Date: Thu, 18 Jun 2026 20:37:29 +0000 Subject: [PATCH] docs: note default Kubernetes version for new clusters --- cloud-accounts/cluster-upgrades.mdx | 10 ++++++++++ 1 file changed, 10 insertions(+) diff --git a/cloud-accounts/cluster-upgrades.mdx b/cloud-accounts/cluster-upgrades.mdx index eb2ba01..4763115 100644 --- a/cloud-accounts/cluster-upgrades.mdx +++ b/cloud-accounts/cluster-upgrades.mdx @@ -32,6 +32,16 @@ More documentation around zero-downtime deployments may be found [here](/applica 3. Maintaining a constant stream of communication around upgrade timelines and statuses. +## Default Kubernetes version + +New clusters provisioned through Porter are created with **Kubernetes v1.35** by default. This applies to all supported cloud providers (AWS EKS, Google Cloud GKE, and Azure AKS). + +You can select a different Kubernetes version when creating a cluster from the Porter dashboard. Supported versions range from v1.27 to v1.35. + + + We recommend keeping the default version unless you have a specific compatibility requirement. Existing clusters are upgraded to newer versions on the schedule described below — you do not need to recreate a cluster to move forward. + + ## Upgrade Calendar Kubernetes follows a release cycle where there are - approximately - three minor version releases a year. Every release is followed by a period where public clouds integrate the new version into their managed Kubernetes offerings and run tests to ensure compatibility with the underlying cloud. Our upgrade calendar is thus dependent on both release cycles. To account for that, we carry out cluster upgrades twice a year, where we "leapfrog" over versions to ensure customer clusters are running the _latest stable_ version of Kubernetes. These are typically carried out once towards the end of Q1/beginning of Q2 and then later towards the end of Q3.