Upgrade to EKS 1.27

aws-samples · Oct 19, 2023 · 33816cf · 33816cf
1 parent 831211c
commit 33816cf
Show file tree

Hide file tree

Showing 4 changed files with 10 additions and 10 deletions.
diff --git a/cluster/eksctl/cluster.yaml b/cluster/eksctl/cluster.yaml
@@ -9,7 +9,7 @@ availabilityZones:
 metadata:
   name: ${EKS_CLUSTER_NAME}
   region: ${AWS_REGION}
-  version: '1.25'
+  version: '1.27'
   tags:
     karpenter.sh/discovery: ${EKS_CLUSTER_NAME}
     created-by: eks-workshop-v2
@@ -26,7 +26,7 @@ vpc:
 
 addons:
 - name: vpc-cni
-  version: v1.12.5-eksbuild.2
+  version: '1.14.1'
   configurationValues: "{\"env\":{\"ENABLE_PREFIX_DELEGATION\":\"true\", \"ENABLE_POD_ENI\":\"true\", \"POD_SECURITY_GROUP_ENFORCING_MODE\":\"standard\"}}"
   resolveConflicts: overwrite
 
@@ -37,6 +37,6 @@ managedNodeGroups:
   maxSize: 6
   instanceType: m5.large
   privateNetworking: true
-  releaseVersion: 1.25.6-20230304
+  releaseVersion: 1.27.3-20230816
   labels:
     workshop-default: 'yes'
diff --git a/website/docs/fundamentals/managed-node-groups/upgrades/index.md b/website/docs/fundamentals/managed-node-groups/upgrades/index.md
@@ -47,7 +47,7 @@ Upgrading the node group will take at least 10 minutes, only execute this sectio
 The EKS cluster that has been provisioned for you intentionally has managed node groups that are not running the latest AMI. You can see what the latest AMI version is by querying SSM:
 
 ```bash
-$ aws ssm get-parameter --name /aws/service/eks/optimized-ami/1.25/amazon-linux-2/recommended/image_id --region $AWS_REGION --query "Parameter.Value" --output text
+$ aws ssm get-parameter --name /aws/service/eks/optimized-ami/1.27/amazon-linux-2/recommended/image_id --region $AWS_REGION --query "Parameter.Value" --output text
 ami-0fcd72f3118e0dd88
 ```
 

diff --git a/website/docs/networking/custom-networking/provision-new-node-group.md b/website/docs/networking/custom-networking/provision-new-node-group.md
@@ -26,10 +26,10 @@ Once this is complete we can see the new nodes registered in the EKS cluster:
 ```bash wait=30
 $ kubectl get nodes -L eks.amazonaws.com/nodegroup
 NAME                                            STATUS   ROLES    AGE   VERSION               NODEGROUP
-ip-10-42-104-242.us-west-2.compute.internal   Ready    <none>   84m   v1.25.6-eks-48e63af   default
-ip-10-42-110-28.us-west-2.compute.internal    Ready    <none>   61s   v1.25.9-eks-0a21954   custom-networking
-ip-10-42-139-60.us-west-2.compute.internal    Ready    <none>   65m   v1.25.6-eks-48e63af   default
-ip-10-42-180-105.us-west-2.compute.internal   Ready    <none>   65m   v1.25.6-eks-48e63af   default
+ip-10-42-104-242.us-west-2.compute.internal     Ready    <none>   84m   vVAR::KUBERNETES_NODE_VERSION   default
+ip-10-42-110-28.us-west-2.compute.internal      Ready    <none>   61s   vVAR::KUBERNETES_NODE_VERSION   custom-networking
+ip-10-42-139-60.us-west-2.compute.internal      Ready    <none>   65m   vVAR::KUBERNETES_NODE_VERSION   default
+ip-10-42-180-105.us-west-2.compute.internal     Ready    <none>   65m   vVAR::KUBERNETES_NODE_VERSION   default
 ```
 
 You can see that 1 new node provisioned labeled with the name of the new node group.
diff --git a/website/docusaurus.config.js b/website/docusaurus.config.js
@@ -57,8 +57,8 @@ const config = {
                 MANIFESTS_REF: manifestsRef,
                 MANIFESTS_OWNER: manifestsOwner,
                 MANIFESTS_REPOSITORY: manifestsRepository,
-                KUBERNETES_VERSION: '1.25',
-                KUBERNETES_NODE_VERSION: '1.25.6-eks-48e63af'
+                KUBERNETES_VERSION: '1.27',
+                KUBERNETES_NODE_VERSION: '1.27.3-eks-48e63af'
               }
             }],
             [remarkIncludeCode, { manifestsDir }],