Kubernetes version notes

Each GKE on AWS release comes with Kubernetes version notes. These are similar to release notes but are specific to a Kubernetes version and might offer more technical detail.

GKE on AWS supports the Kubernetes versions listed in the following sections. If a version isn't included in this file, it's unsupported.

Kubernetes 1.30

1.30.4-gke.400

Kubernetes OSS release notes

1.30.3-gke.100

Kubernetes OSS release notes

  • Feature: Added kubeletConfig node system configuration. With this feature, you can specify custom configurations on your node pools, including CPU manager policy, CPU throttling, and process IDs (PIDs).

  • Feature: The gcloud beta container fleet memberships get-credentials command uses a preview feature of the Connect gateway that lets you run the kubectl attach, cp, and exec commands. For more information, see Limitations in the Connect gateway documentation.

  • Security Fixes:

Kubernetes 1.29

1.29.8-gke.600

Kubernetes OSS release notes

1.29.7-gke.100

Kubernetes OSS release notes

1.29.6-gke.600

Kubernetes OSS release notes

1.29.5-gke.1100

Kubernetes OSS release notes

1.29.5-gke.700

Kubernetes OSS release notes

1.29.4-gke.200

Kubernetes OSS release notes

1.29.3-gke.600

Kubernetes OSS release notes.

Kubernetes 1.28

1.28.13-gke.600

Kubernetes OSS release notes

1.28.12-gke.100

Kubernetes OSS release notes

1.28.11-gke.600

Kubernetes OSS release notes

1.28.10-gke.1300

Kubernetes OSS release notes

1.28.10-gke.800

Kubernetes OSS release notes

1.28.9-gke.400

Kubernetes OSS release notes

1.28.8-gke.800

Kubernetes OSS release notes.

1.28.7-gke.1700

Kubernetes OSS release notes

  • Bug Fix: Fixed an issue where the Instance Metadata Service (IMDS) emulator sometimes failed to bind to an IP address on the node. The IMDS emulator enables nodes to securely access AWS EC2 instance metadata.

1.28.5-gke.1200

Kubernetes OSS release notes

1.28.5-gke.100

Kubernetes OSS release notes

1.28.3-gke.700

Kubernetes OSS release notes

  • Breaking Change: Starting from Kubernetes 1.28, clusters require outbound HTTPS connectivity to {GCP_LOCATION}-gkemulticloud.googleapis.com. Ensure your proxy server and/or firewall allows for this traffic.

  • Breaking Change: Starting from Kubernetes 1.28, the Multi-Cloud API service agent role requires a new Iam:getinstanceprofile permission on your AWS project. This permission is used by the Multi-Cloud Service to inspect the instance profiles attached to in-cluster Virtual Machine Instances.

  • Feature: Added rollback support for AWS node pools that have failed update operations. This allows customers to revert node pools back to their original state.

  • Feature: Added support for pulling images from private Google Artifact Registry and private Google Container Registry without exported Google Service Account key. The image pull credentials are managed and automatically rotated by Google.

  • Feature: Removed the need to explicitly add Google IAM bindings for most features.

    1. No longer need to add any bindings for gke-system/gke-telemetry-agent when creating a cluster.
    2. No longer need to add any bindings for gmp-system/collector or gmp-system/rule-evaluator when enabling managed data collection for Google Managed Service for Prometheus.
    3. No longer need to add any bindings for gke-system/binauthz-agent when enabling binary authorization.

  • Feature: AWS Surge update is now Generally Available. Surge updates allow you to configure the speed and disruption of node pool updates. For more details about how to enable and configure Surge settings on your AWS node pools, see Configure Surge updates of node pools.

  • Feature: Upgraded the kernel for Ubuntu 22.04 to linux-aws 6.2.

  • Feature: Added support for creating node pools using the following AWS EC2 instances: G5, I4g, M7a, M7g, M7i, R7g, R7i, and R7iz.

  • Bug Fix: Improved launch template creation. Tags provided by customers are propagated to instances.

    • This change primarily enhances support for IAM policy rules. It specifically addresses rules that prohibit the use of launch templates which don't support tag propagation, even in cases where the associated Auto Scaling Group (ASG) does propagate tags.
    • This can be a breaking change, depending on the specifics of the customer's IAM policy regarding tag checks. Therefore, it's important to exercise caution during the upgrade process, as improper handling may leave a cluster in a degraded state.
    • Action ec2:CreateTags on resource arn:aws:ec2:*:*:instance/* is required for the Anthos Multi-Cloud API service agent role. Please check https://cloud.google.com/kubernetes-engine/multi-cloud/docs/aws/how-to/create-aws-iam-roles#create_service_agent_role for latest info.
    • We suggest customers try creating a throw-away 1.28 cluster and confirm that IAM policies work correctly before attempting to upgrade to 1.28.

  • Bug Fix: Upgrading a cluster to version 1.28 will clean up obsolete resources that may have been created in older versions (up to 1.25) but are no longer relevant. The following resources in the namespace gke-system are deleted if they exist:

    • daemonsets fluentbit-gke-windows and gke-metrics-agent-windows
    • configmaps fluentbit-gke-windows-config and gke-metrics-agent-windows-conf

  • Bug Fix: Enhanced Cloud Logging's ingestion of logs from Anthos clusters on AWS:

    • Fixed an issue in timestamp parsing.
    • Assigned the correct severity level to the anthos-metadata-agent's error logs.

  • Security Fixes