Skip to content

Update EKS version to 1.34 and kubectl to 1.34.4 #108

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
jrgwv merged 1 commit into from
Apr 15, 2026
+3 −3
Merged

Update EKS version to 1.34 and kubectl to 1.34.4 #108

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion scripts/setup-ws-instance-python.sh
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -45,7 +45,7 @@ eksctl version

## Install kubectl
# https://docs.aws.amazon.com/eks/latest/userguide/install-kubectl.html
curl -O https://s3.us-west-2.amazonaws.com/amazon-eks/1.30.0/2024-05-12/bin/linux/amd64/kubectl
curl -O https://s3.us-west-2.amazonaws.com/amazon-eks/1.34.4/2026-02-27/bin/linux/amd64/kubectl
chmod +x ./kubectl
mkdir -p $HOME/bin && cp ./kubectl $HOME/bin/kubectl && export PATH=$PATH:$HOME/bin
echo 'export PATH=$PATH:$HOME/bin' >> ~/.bashrc
Expand Down
4 changes: 2 additions & 2 deletions website/docs/python/eks/create-cluster.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -18,7 +18,7 @@ Creating an Amazon EKS cluster with [eksctl](https://eksctl.io/) allows for a wi
## 1. Using the cluster configuration file for EKS Auto Mode nodes
The **[create-automode-python.yaml](https://github.com/aws-samples/python-fastapi-demo-docker/blob/main/eks/create-automode-python.yaml)** eksctl configuration file sets up an EKS Auto Mode-based cluster for deploying our [python-fastapi-demo-docker](https://github.com/aws-samples/python-fastapi-demo-docker) with the following components:

- **Metadata**: This section contains crucial metadata about your cluster, such as the cluster's name ("automode-quickstart"), the AWS region where the cluster will be hosted ("us-east-1"), and the Kubernetes version ("1.32") that the cluster will run.
- **Metadata**: This section contains crucial metadata about your cluster, such as the cluster's name ("automode-quickstart"), the AWS region where the cluster will be hosted ("us-east-1"), and the Kubernetes version ("1.34") that the cluster will run.
- **AutoMode config**: This section describes configurations such as enabling EKS Auto Mode, specifying node roles, and defining NodePool resources. If you omit node roles and NodePool, eksctl will automatically create default ones.
- **Permissions (IAM)**: This section outlines how the configuration utilizes IAM roles for service accounts through an [OpenID Connect (OIDC) identity provider](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_providers_create_oidc.html). A service account is established here: `adot-collector`, which has permissions to send tracing data to AWS X-Ray.
- **Logs (CloudWatch)**: The configuration wraps up with a `cloudWatch` section, which sets up [Amazon CloudWatch](https://aws.amazon.com/cloudwatch/) logging for the cluster. All categories of Kubernetes control plane logs are enabled and are set to be retained for 30 days.
Expand Down Expand Up @@ -79,7 +79,7 @@ This lab has walked you through the process of creating an Amazon EKS Auto Mode
## 1. Using the cluster configuration file for Managed Node Groups
The **[create-mng-python.yaml](https://github.com/aws-samples/python-fastapi-demo-docker/blob/main/eks/create-mng-python.yaml)** eksctl configuration file sets up a managed node groups-based cluster for deploying our [python-fastapi-demo-docker](https://github.com/aws-samples/python-fastapi-demo-docker) with the following components:

- **Metadata**: This section contains crucial metadata about your cluster, such as the cluster's name ("managednode-quickstart"), the target AWS region ("us-east-1"), and the Kubernetes version ("1.32") to be deployed.
- **Metadata**: This section contains crucial metadata about your cluster, such as the cluster's name ("managednode-quickstart"), the target AWS region ("us-east-1"), and the Kubernetes version ("1.34") to be deployed.
- **Permissions (IAM)**: This section outlines how the configuration utilizes IAM roles for service accounts through an [OpenID Connect (OIDC) identity provider](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_providers_create_oidc.html). Two service accounts are established here: `aws-load-balancer-controller`, which authorizes Kubernetes to manage the [AWS Load Balancer Controller (LBC)](https://kubernetes-sigs.github.io/aws-load-balancer-controller/), `adot-collector`, which has permissions to send tracing data to AWS X-Ray.
- **Managed node groups**: This section defines a managed node group called `eks-mng`. Nodes within this group are based on `t3.medium` instance types, with an initial deployment of two nodes. For more instance types, see [Amazon EC2 Instance Types](https://aws.amazon.com/ec2/instance-types/).
- **Managed add-ons**: The configuration contains an `addons` section, which defines the [EKS add-ons](https://docs.aws.amazon.com/eks/latest/userguide/eks-add-ons.html) to be enabled on the cluster. In this case, `kube-proxy`, `vpc-cni` (a networking plugin for pods in VPC), and `coredns` (a DNS server) are activated. The `vpc-cni` addon is additionally linked with the [AmazonEKS_CNI_Policy](https://docs.aws.amazon.com/aws-managed-policy/latest/reference/AmazonEKS_CNI_Policy.html) policy.
Expand Down
Loading