GKE on AWS release notes

This page documents production updates to GKE on AWS. Check this page for announcements about new or updated features, bug fixes, known issues, and deprecated functionality.

You can see the latest product updates for all of Google Cloud on the Google Cloud page, browse and filter all release notes in the Google Cloud console, or programmatically access release notes in BigQuery.

To get the latest product updates delivered to you, add the URL of this page to your feed reader, or add the feed URL directly: http://cloud.google.com/feeds/anthos-clusters-on-aws-release-notes.xml

June 11, 2024

The following vulnerabilities were discovered in the Linux kernel that can lead to a privilege escalation on Container-Optimized OS nodes:

  • CVE-2024-26583

For more information, see the GCP-2024-034 security bulletin.

June 10, 2024

The following vulnerabilities were discovered in the Linux kernel that can lead to a privilege escalation on Container-Optimized OS nodes:

  • CVE-2022-23222

For more information, see the GCP-2024-033 security bulletin.

June 06, 2024

You can now launch clusters with the following Kubernetes versions. Click on the following links to see the release notes associated with these patches:

May 27, 2024

A new vulnerability (CVE-2024-4323) has been discovered in Fluent Bit that could result in remote code execution. Fluent Bit versions 2.0.7 through 3.0.3 are affected.

GKE on AWS doesn't use a vulnerable version of Fluent Bit and is unaffected.

For more information, see the GCP-2024-031 security bulletin.

May 15, 2024

A vulnerability (CVE-2023-52620) was discovered in the Linux kernel that can lead to a privilege escalation on Container-Optimized OS and Ubuntu nodes.

For more information, see the GCP-2024-030 security bulletin.

May 14, 2024

A vulnerability (CVE-2024-26581) was discovered in the Linux kernel that can lead to a privilege escalation on Container-Optimized OS and Ubuntu nodes.

For more information, see the GCP-2024-028 security bulletin.

A vulnerability (CVE-2024-26642) was discovered in the Linux kernel that can lead to a privilege escalation on Container-Optimized OS and Ubuntu nodes.

For more information, see the GCP-2024-029 security bulletin.

May 09, 2024

You can now launch clusters with the following Kubernetes versions. Click on the following links to see the release notes associated with these patches:

GKE on AWS now supports clusters in the ap-northeast-2 region. For more information, see Supported regions.

May 08, 2024

A vulnerability (CVE-2024-26808) was discovered in the Linux kernel that can lead to a privilege escalation on Container-Optimized OS and Ubuntu nodes.

For more information, see the GCP-2024-027 security bulletin.

May 07, 2024

A vulnerability (CVE-2024-26643) was discovered in the Linux kernel that can lead to a privilege escalation on Container-Optimized OS and Ubuntu nodes.

For more information, see the GCP-2024-026 security bulletin.

April 30, 2024

GKE on AWS now supports clusters in the ap-northeast-2 region. For more information, see Supported regions.

April 25, 2024

A vulnerability (CVE-2024-26585) was discovered in the Linux kernel that can lead to a privilege escalation on Container-Optimized OS and Ubuntu nodes. For more information, see the GCP-2024-024 security bulletin.

April 04, 2024

You can now launch clusters with the following Kubernetes versions. Click on the following links to see the release notes associated with these patches:

April 03, 2024

A Denial-of-Service (DoS) vulnerability (CVE-2023-45288) was recently discovered in multiple implementations of the HTTP/2 protocol, including the golang HTTP server used by Kubernetes. The vulnerability could lead to a DoS of the Google Kubernetes Engine (GKE) control plane. For more information, see the GCP-2024-022 security bulletin.

March 05, 2024

You can now launch clusters with the following Kubernetes versions. Click on the following links to see the release notes associated with these patches:

February 26, 2024

The following vulnerabilities were discovered in the Linux kernel that can lead to a privilege escalation on Container-Optimized OS and Ubuntu nodes:

The following vulnerabilities were discovered in the Linux kernel that can lead to a privilege escalation on Container-Optimized OS and Ubuntu nodes:

  • CVE-2024-0193

For more information, see the GCP-2024-013 security bulletin.

The following vulnerabilities were discovered in the Linux kernel that can lead to a privilege escalation on Container-Optimized OS and Ubuntu nodes:

  • CVE-2023-6932

For more information, see the GCP-2024-011 security bulletin.

The following vulnerabilities were discovered in the Linux kernel that can lead to a privilege escalation on Container-Optimized OS and Ubuntu nodes.

  • CVE-2023-6931

For more information, see the GCP-2024-010 security bulletin.

The following vulnerabilities were discovered in the Linux kernel that can lead to a privilege escalation on Container-Optimized OS and Ubuntu nodes.

  • CVE-2023-6817

For more information, see the GCP-2024-004 security bulletin.

February 05, 2024

You can now launch clusters with the following Kubernetes versions. Click on the following links to see the release notes associated with these patches:

January 17, 2024

The following vulnerabilities were discovered in the Linux kernel that can lead to a privilege escalation on Container-Optimized OS nodes.

  • CVE-2023-6111

For instructions and more details, see the GCP-2024-002 security bulletin.

December 14, 2023

You can now launch clusters with the following Kubernetes versions. Click on the following links to see the release notes associated with these patches:

November 14, 2023

The following vulnerabilities were discovered in the Linux kernel that can lead to a privilege escalation on Container-Optimized OS and Ubuntu nodes.

  • CVE-2023-4147

For more information, see the GCP-2023-042 security bulletin.

November 08, 2023

A vulnerability (CVE-2023-4004) has been discovered in the Linux kernel that can lead to a privilege escalation on Container-Optimized OS and Ubuntu nodes. For more information, see the GCP-2023-041 security bulletin.

October 30, 2023

You can now launch clusters with the following Kubernetes versions. Click on the following links to see the release notes associated with these patches:

October 02, 2023

You can now launch clusters with the following Kubernetes versions. Click on the following links to see the release notes associated with these patches:

September 06, 2023

You can now launch clusters with the following Kubernetes versions:

  • 1.25.8-gke.500
  • 1.26.7-gke.500
  • 1.27.4-gke.1600

1.27

  • Preview: Enabled surge updates. Surge updates allow you to configure the speed and disruption of node pool updates. Please contact your account team to opt into the preview.

  • GA: Added support for AWS spot instance node pools. Creating AWS spot node pools is now GA. Spot instance node pools are pools of Amazon EC2 Spot Instances that are available on AWS at a lower cost.

  • GA: Enabled node auto repair. This feature continuously monitors the health of each node in a node pool.

  • Added Binary Authorization support which is a deploy-time security control that ensures only trusted container images are deployed. With Binary Authorization, you can require images to be signed by trusted authorities during the development process and then enforce signature validation when deploying. By enforcing validation, you can gain tighter control over your container environment by ensuring only verified images are integrated into the build-and-release process. For details about how to enable Binary Authorization on your clusters, see How to enable Binary Authorization.

  • Added support for a new admin-groups flag in the create and update APIs. This flag allows customers to quickly and easily authenticate listed groups as cluster administrators, eliminating the need to manually create and apply RBAC policies.

  • Added an ignore_errors option to the delete API to handle cases where accidentally deleted IAM roles or manual removal of resources prevent the deletion of clusters or node pools. By appending ?ignore_errors=true to the DELETE request URL, users can now forcibly remove clusters or node pools. However, this approach might result in orphaned resources in AWS or Azure, requiring manual cleanup.

  • Upgraded the snapshot-controller and csi-snapshot-validation-webhook to v6.2.2. This new version introduces an important change to the API. Specifically, the VolumeSnapshot, VolumeSnapshotContents, and VolumeSnapshotClass v1beta1 APIs are no longer available.

  • Disabled the unauthenticated kubelet read-only port 10255. Once a node pool is upgraded to version 1.27, workloads running on it will no longer be able to connect to port 10255.

  • Enabled gzip compression for fluent-bit's ingestion of logs into Cloud Logging. This improves the efficiency of log transfer for both the control plane and workloads.

  • Optimized audit-proxy's audit Logging ingestion by enabling gzip compression.

  • Improved security by adding file-integrity checks and fingerprint validation for Google-managed binary artifacts downloaded from Cloud Storage.

  • Added support for automatic periodic defragmentation of etcd and etcd-events on the control plane. This feature reduces unnecessary disk storage and helps to prevent etcd and the control plane from becoming unavailable due to disk storage issues.

  • Changed the metrics names for Kubernetes resource metrics to use a metrics prefix of kubernetes.io/anthos/ rather than kubernetes.io/. For details refer to the metrics reference documentation.

  • Changed default etcd version to v3.4.21 on new clusters for improved stability. Existing clusters upgraded to this version will use etcd v3.5.6.

  • Improved node resource management by reserving resources for the kubelet. While this feature is crucial for preventing Out of Memory (OOM) errors by ensuring system and Kubernetes processes have the resources they need, it may lead to workload disruptions. The reservation of resources for the kubelet may affect the available resources for Pods, potentially affecting the capacity of smaller nodes to handle existing workloads. Customers should verify that smaller nodes can still support their workloads with this new feature activated.

    • The reserved memory percentages are as follows:
      • 255 MiB for machines with less than 1GB of memory
      • 25% of the first 4GB of memory
      • 20% of the next 4GB
      • 10% of the next 8GB
      • 6% of the next 112GB
      • 2% of any memory above 128GB
    • The reserved CPU percentages are as follows:
      • 6% of the first core
      • 1% of the next core
      • 0.5% of the next 2 cores
      • 0.25% of any cores above 4 cores

Enabled the cluster autoscaler to balance nodes across different availability zones. This is achieved using the --balance-similar-node-groups flag.

1.25

Expanded the list of metrics collected from node pools to include gke-metrics-agent, cilium-agent, cilium-operator, coredns, fluentbit-gke, kubelet, and konnectivity-agent.

August 03, 2023

You can now launch clusters with the following Kubernetes versions. Click on the following links to see the release notes associated with these patches:

Anthos Multi-Cloud is disabling the unauthenticated kubelet read-only port 10255 for node pools in our next minor release with Kubernetes v1.27. This port is unauthenticated, which means potentially sensitive information passed via this port over HTTP is accessible. Once a node pool is upgraded to version 1.27, workloads running on it will no longer be able to connect to port 10255.

To determine if you have dependencies on this port, check the metrics in a Kubernetes v1.26 cluster that is running Kubernetes v1.26 node pools.

If you have dependencies on this port, perform the following steps:

  1. Update the workload to access https://:10250 instead of http://:10255.

  2. Authenticate to kubelet using a service account.

  3. Widen the RBAC rules so that this service account has sufficient permissions to request the needed kubelet APIs.

Note that popular third-party products should already support kubelet authentication, and may require no action beyond upgrade.

If you have a cluster which has dependencies on the read-only port 10255 and you aren't able to migrate, please reach out to the Anthos Multi-Cloud team.

July 13, 2023

You can now launch clusters with the following Kubernetes versions:

  • 1.24.14-gke.1400
  • 1.25.10-gke.1200
  • 1.26.5-gke.1200

1.24, 1.25, 1.26

Configured the cluster autoscaler to balance the number of nodes across availability zones using the parameter --balance-similar-node-groups.

1.25

Migrated node pool metrics agent and metrics server to authenticated kubelet port.

1.26

Fixed an issue where Kubernetes 1.26.2 incorrectly applied the default StorageClass to PersistentVolumeClaims with the deprecated annotation volume.beta.kubernetes.io/storage-class. (This issue is also fixed in release 1.15.1.)

This release fixes the following vulnerabilities:

Applications may experience timeouts due to netfilter connection tracking (conntrack) table insertion failures. Insertion failures can occur even when the conntrack table has room for new entries. The failures are caused by changes in kernel 5.15 and higher that restrict table insertions based on chain length.

June 27, 2023

With CVE-2023-31436, an out-of-bounds memory access flaw was found in the Linux kernel's traffic control (QoS) subsystem in how a user triggers the qfq_change_class function with an incorrect MTU value of the network device used as lmax. This flaw allows a local user to crash or potentially escalate their privileges on the system.

For more information, see the GCP-2023-017 security bulletin.

A new vulnerability (CVE-2023-2235) has been discovered in the Linux kernel that can lead to a privilege escalation on the node. For more information, see the GCP-2023-018 security bulletin.

June 06, 2023

Security bulletin

A new vulnerability (CVE-2023-2878) has been discovered in the secrets-store-csi-driver where an actor with access to the driver logs could observe service account tokens. These tokens could then potentially be exchanged with external cloud providers to access secrets stored in cloud vault solutions. For more information, see the GCP-2023-009 security bulletin.

June 05, 2023

You can now launch clusters with the following Kubernetes versions:

  • 1.24.13-gke.500
  • 1.25.8-gke.500
  • 1.26.4-gke.2200

Security bulletin

A new vulnerability (CVE-2023-1872) has been discovered in the Linux kernel that can lead to a privilege escalation to root on the node. For more information, see the GCP-2023-008.

1.26

Fixed an issue where Kubernetes 1.26.2 incorrectly applied the default StorageClass to PersistentVolumeClaims with the deprecated annotation volume.beta.kubernetes.io/storage-class.

This release fixes the following vulnerability:

For information about the latest known issues, see Known issues for Anthos clusters on AWS.

May 18, 2023

Security bulletin

Two new vulnerabilities (CVE-2023-1281, CVE-2023-1829) have been discovered in the Linux kernel that can lead to a privilege escalation to root on the node. For more information, see the GCP-2023-005 security bulletin.

May 04, 2023

You can now launch clusters with the following Kubernetes versions:

  • 1.24.11-gke.1000
  • 1.25.7-gke.1000
  • 1.26.2-gke.1001
  • Updated OS image to Ubuntu 22.04. cgroupv2 is now used as the default control group configuration.

    • Ubuntu 22.04 uses cgroupv2 by default. We recommend that you check if any of your applications access the cgroup filesystem. If they do, they must be updated to use cgroupv2.
  • Improved monitoring by exporting metrics for control plane components.

  • Enabled sending Kubernetes resource metadata to Google Cloud Platform, improving both the user interface and cluster metrics. For the metadata to be ingested properly, customers need to enable the Config Monitoring for Ops API.

  • Enabled kubelet graceful node shutdown. Non-system Pods are given 15 seconds to terminate, after which system Pods (with the system-cluster-critical or system-node-critical priority classes) have 15 seconds to gracefully terminate.

  • Newly-created clusters now use etcd v3.4.21 for improved stability. Existing clusters of previous versions were already using etcd v3.5.x and will not be downgraded to v3.4.21 during cluster upgrade; these clusters will instead use v3.5.6.

  • Clusters now have per-node-pool subnet security group rules instead of VPC-wide rules:

    • Previously, the control plane allowed inbound traffic from the entire primary IP range of the VPC on ports TCP/443 and TCP/8123, which are used by node pools.
    • Now, the control plane narrows the allowed inbound traffic to each IP range of the node pool subnets on ports TCP/443 and TCP/8123; multiple node pools can share one subnet.
    • This change supports node pools running outside of the VPC's primary IP range and improves the security of the control plane.
    • If you relied on the VPC-wide security group rule for allowing traffic from outside of the cluster (e.g. from a bastion host for kubectl), then as part of the upgrade you should create a security group, add a VPC-wide rule to it, and attach the security group to the control plane (via the AwsCluster.controlPlane.securityGroupIds field).
  • Preview: Enabled node auto repair. This feature continuously monitors the health of each node in a node pool. Please contact your account team to opt into the preview.

  • Preview: Added support for AWS spot instance node pools. Spot instance node pools are pools of Amazon EC2 Spot Instances that are available on AWS at a lower cost.

  • GA: Enabled node pool creation with ARM-based (Graviton) instance types.

  • Kubernetes 1.26.2 will incorrectly apply the default StorageClass to PersistentVolumeClaims which have the deprecated annotation volume.beta.kubernetes.io/storage-class.

  • Applications may experience timeouts due to netfilter connection tracking (conntrack) table insertion failures. Insertion failures can occur even when the conntrack table has room for new entries. The failures are caused by changes in kernel 5.15 and higher that restrict table insertions based on chain length.

April 12, 2023

Kubernetes image registry redirect

As of March 21, 2023, traffic to k8s.gcr.io is redirected to registry.k8s.io, following the community announcement. This change is happening gradually to reduce disruption, and should be transparent for most Anthos clusters.

To check for edge cases and mitigate potential impact to your clusters, follow the step-by-step guidance in k8s.gcr.io Redirect to registry.k8s.io - What You Need to Know.

April 05, 2023

You can now launch clusters with the following Kubernetes versions:

  • 1.23.16-gke.2800
  • 1.24.10-gke.1200
  • 1.25.6-gke.1600
  • Fixed an issue that could cause cluster upgrades to fail if certain types of validating admission webhooks are registered.
  • (1.24 only) Fixed Cilium security ID propagation so that IDs are properly passed in the tunnel header when requests are forwarded to Services of type NodePort and LoadBalancer.

March 07, 2023

You can now launch clusters with the following Kubernetes versions:

  • 1.23.16-gke.200
  • 1.24.9-gke.2000
  • 1.25.5-gke.2000
  • Fixed an issue where certain errors weren't propagated and reported during cluster create/update operations.
  • Fixed an issue with AWS EFS CSI driver where EFS hostnames can't be resolved when AWS VPC is configured to use a custom DNS server.
  • Updated Anthos Identity Service to better handle concurrent authentication webhook requests.
  • Updated fluent-bit to v1.9.9 to fix CVE-2022-42898.

This release fixes the following vulnerabilities:

February 01, 2023

You can now launch clusters with the following Kubernetes versions:

  • 1.23.14-gke.1800
  • 1.24.9-gke.1500
  • 1.25.5-gke.1500
  • Upgraded containerd to version 1.6.12.
  • Upgraded storage drivers.

This release fixes the following vulnerabilities:

December 21, 2022

A new vulnerability (CVE-2022-2602) has been discovered in the io_uring subsystem in the Linux kernel that can allow an attacker to potentially execute arbitrary code. For more information, see the GCP-2022-2025 security bulletin.

December 15, 2022

You can now launch clusters with the following Kubernetes versions:

  • 1.23.14-gke.1100
  • 1.24.8-gke.1300
  • 1.25.4-gke.1300

You can now dynamically update AWS node pool security groups. To do so your API role must have the ec2:ModifyInstanceAttribute and ec2:DescribeInstances permissions.

You can now dynamically updating AWS node pool tags. To do so, your API role must have the autoscaling:CreateOrUpdateTags, autoscaling:DeleteTags, ec2:CreateTags, ec2:DeleteTags, and ec2:DescribeLaunchTemplates permissions.

Elastic File System (EFS) dynamic provisioning is now available in GA for clusters at version 1.25 or later. To use this feature, you must add the following permissions to the control plane role:

  • ec2:DescribeAvailabilityZones
  • elasticfilesystem:DescribeAccessPoints
  • elasticfilesystem:DescribeFileSystems
  • elasticfilesystem:DescribeMountTargets
  • elasticfilesystem:CreateAccessPoint
  • elasticfilesystem:DeleteAccessPoint

You can now upload workload metrics using Google Managed Service for Prometheus with managed collection to Cloud Monarch. This has been upgraded from a preview feature to GA.

You can now enable and update CloudWatch metrics collection on AWS node pool's auto scaling group. To use this feature your API role must have the autoscaling:EnableMetricsCollection and autoscaling:DisableMetricsCollection permissions.

Added a new token manager (gke-token-manager) to generate tokens for control plane components. This eliminates a control-plane component dependency on kube-apiserver, removes the need for RBAC in token generation, and permits logging to begin earlier in the startup cycle.

As a preview feature, Google Cloud Monitoring can now ingest a set of control plane metrics from kube-apiserver, kube-scheduler, kube-controller manager and etcd.

Administrators can grant AWS cluster access to all members of a Google Group by granting the required RBAC permission to the group. For details, see Set up the Connect gateway with Google Groups.

To use the following features with gcloud requires gcloud v413.0.0, scheduled for release in January 2023. You can access these features through the API now:

  • Dynamically updating AWS node pool tags
  • Enable and update CloudWatch metrics collection on AWS node pools

Static pods running on the cluster's control plane VMs are now restricted to run as non-root Linux users.

Fixed an issue in which outdated versions of gke-connect-agent were not always removed after cluster upgrades.

Kubernetes 1.22 versions are no longer supported. To upgrade to a supported version, see Upgrade your AWS cluster version.

Kubernetes version 1.25 deprecates several APIs. For details, see the Kubernetes Deprecated API Migration Guide.

November 10, 2022

Two new vulnerabilities (CVE-2022-2585 and CVE-2022-2588) have been discovered in the Linux kernel that can lead to a full container break out to root on the node.

For more information, see the GCP-2022-024 security bulletin.

November 03, 2022

You can now launch clusters with the following Kubernetes versions:

  • 1.22.15-gke.100
  • 1.23.11-gke.300
  • 1.24.5-gke.200

Anthos on AWS nodepools now includes the iptables utility to resolve an issue with the installation of Anthos Service Mesh.

On clusters at version 1.24.3-gke.2200, the IMDS emulator fails to start. This issue is fixed for clusters at version 1.24.5-gke.200 and later.

October 28, 2022

A new vulnerability, CVE-2022-3176, has been discovered in the Linux kernel that can lead to local privilege escalation. This vulnerability allows an unprivileged user to achieve full container breakout to root on the node.

For instructions and more details, see the Anthos clusters on AWS security bulletin.

October 14, 2022

Creating a Kubernetes Service resource with type LoadBalancer and annotation service.beta.kubernetes.io/aws-load-balancer-type: nlb in a version 1.23 or 1.24 cluster would create a network load balancer whose target group would remain empty. This issue is resolved in the new Kubernetes patch versions 1.23.9-gke.2200 and 1.24.3-gke.2200.

September 29, 2022

You can now launch clusters with the following Kubernetes versions:

  • 1.24.3-gke.2100
  • 1.23.9-gke.2100
  • 1.22.12-gke.2300

Kubernetes 1.21 versions are no longer supported. To upgrade to a supported version, see Upgrade your AWS cluster version.

You can now use the Google Cloud console to update, upgrade, and delete clusters on AWS.

Creating Arm node pools is now a preview feature. To learn more, see Run Arm workloads in Anthos clusters on AWS.

If you have legacy workloads that don't support Workload Identity directly, you can now use the IMDS emulator to access IMDS data. To learn more, see Enable the IMDS emulator.

In Kubernetes version 1.24 and later, Google Cloud Managed Service for Prometheus (GMP) is available as an invite only private preview. GMP lets you monitor and alert on workloads, using Prometheus, without having to manually manage and operate Prometheus at scale.

Anthos clusters on AWS now supports Cloud Monitoring for Windows node pools from Kubernetes version 1.24 and later. To learn more about monitoring in Anthos Clusters on AWS, see Cloud monitoring.

In Kubernetes version 1.24 and later, Anthos clusters on AWS supports EFS dynamic provisioning in preview mode. To use this feature, you must add the following permissions to the control plane role:

  • ec2:DescribeAvailabilityZones
  • elasticfilesystem:DescribeAccessPoints
  • elasticfilesystem:DescribeFileSystems
  • elasticfilesystem:DescribeMountTargets
  • elasticfilesystem:CreateAccessPoint
  • elasticfilesystem:DeleteAccessPoint

To learn more, see Update your AWS cluster parameters.

This release of Anthos Clusters on AWS supports updating your control plane tags on Kubernetes clusters with a version of 1.24 or later. Supported Kubernetes cluster versions describes the required IAM permission changes. This entry was added to the release notes on October 4, 2022.

In Kubernetes version 1.24 and later, there are now checks to the API to ensure that users aren't making inconsistent or erroneous requests.

Go 1.18 stops accepting certificates signed with the SHA-1 hash algorithm by default. Admission and conversion webhooks or aggregated server endpoints using these insecure certificates will break by default starting from Kubertnetes version 1.24.

The environment variable GODEBUG=x509sha1=1 is set in Anthos on AWS clusters as a temporary workaround to let these insecure certificates continue to work. However, the Go team is anticipated to remove support on this workaround. You should check and ensure there aren't any admission or conversion webhooks or aggregated server endpoints that are using such insecure certificates before upgrading to the upcoming breaking version.

Anthos Service Mesh doesn't work on Anthos Clusters on AWS when Anthos Service Mesh has the Istio Container Network Interface (CNI) enabled. To use Anthos Service Mesh with this product, disable CNI in Anthos Service Mesh.

August 29, 2022

You can now launch clusters with the following Kubernetes versions:

  • 1.21.14-gke.2900
  • 1.22.12-gke.1100
  • 1.23.9-gke.800

August 04, 2022

You can now launch clusters with the following Kubernetes versions:

  • 1.23.8-gke.1700
  • 1.22.12-gke.200
  • 1.21.14-gke.2100

This release fixes the following vulnerabilities:

This list has been updated to include CVE-2022-2327.

August 01, 2022

A new vulnerability (CVE-2022-2327) has been discovered in the Linux kernel that can lead to local privilege escalation. This vulnerability allows an unprivileged user to achieve a full container breakout to root on the node.
For more information, see the GCP-2022-018 security bulletin.

July 13, 2022

You can now launch Kubernetes 1.23 clusters.

Kubernetes 1.23.7-gke.1300 includes the following changes:

  • Disable profiling endpoint (/debug/pprof) by default in kube-scheduler and kube-controller-manager.
  • Update kube-apiserver and kubelet to only use Strong Cryptographic Ciphers.
  • Add an instance metadata server (IMDS) emulator.

In a future release of 1.23 VolumeSnapshot v1beta1 APIs will no longer be served. Please update to VolumeSnapshot v1 APIs as soon as possible.

You can now launch clusters with the following Kubernetes versions:

  • 1.23.7-gke.1300
  • 1.22.10-gke.1500
  • 1.21.11-gke.1900

In Kubernetes 1.23 and higher, cluster Cloud Audit Logs is now available and is enabled by default.

CIS benchmarks are now available for Kubernetes 1.23 clusters.

This release fixes the following vulnerabilities:

Restrictions on IP ranges that can be used for a cluster's Pods and Services are now relaxed. Pod and Service IP ranges can now overlap with VPC's IP ranges, provided they do not intersect the control plane or node pool subnets.

June 23, 2022

Three new memory corruption vulnerabilities (CVE-2022-29581, CVE-2022-29582, CVE-2022-1116) have been discovered in the Linux kernel. These vulnerabilities allow an unprivileged user with local access to the cluster to achieve a full container breakout to root on the node. For more information, refer to the GCP-2022-016 security bulletin.

June 06, 2022

You can now launch clusters with the following Kubernetes versions:

  • 1.21.11-gke.1800
  • 1.22.8-gke.2100

Windows nodes on 1.22.8-gke.2100 now use pigz to improve image layer extraction performance.

May 09, 2022

You can now launch clusters with Kubernetes versions 1.21.11-gke.1100 and 1.22.8-gke.1300

In 1.22.8-gke.1300, fixed an issue where add ons cannot be applied when Windows node pools are enabled.

In 1.22.8-gke.1300, fixed an issue where logging agent could fill up attached disk space.

These releases includes the following Role-based access control (RBAC) changes:

  • Scoped down anet-operator permissions for Lease update.
  • Scoped down anetd Daemonset permissions for Nodes and pods.
  • Scoped down fluentbit-gke permissions for service account tokens.
  • Scoped down gke-metrics-agent for service account tokens.
  • Scoped down coredns-autoscaler permissions for Nodes, ConfigMaps and Deployments.

These releases fix the following CVEs:

April 26, 2022

Two security vulnerabilities, CVE-2022-1055 and CVE-2022-27666 have been discovered in the Linux kernel. Each can lead to a local attacker being able to perform a container breakout, privilege escalation on the host, or both. These vulnerabilities affect all GKE node operating systems (Container-Optimized OS and Ubuntu). For instructions and more details, see the GCP-2022-014 security bulletin.

April 13, 2022

Anthos Clusters on AWS now supports Kubernetes versions 1.22.8-gke.200 and 1.21.11-gke.100. For more information, see the open source release notes for Kubernetes 1.22.8 and Kubernetes 1.21.11.

Kubernetes 1.22 removes support for several deprecated v1beta1 APIs. Before upgrading your clusters to v1.22, you must upgrade your workloads to use the stable v1 APIs and confirm their compatibility with v1.22. For more information, see Kubernetes 1.22 Deprecated APIs.

When you create a new cluster using Kubernetes version 1.22, you can now configure custom logging parameters.

As a preview feature, you can now choose Windows as your node pool image type when you create node pools with Kubernetes version 1.22.8.

You can now set the autoscaler's minimum node count to zero.

This release of Anthos Clusters on AWS improves your ability to update your cluster configuration, including

You can now view most common asynchronous cluster and nodepool boot errors in the long running operation error field.

As a preview feature, you can now configure nodes to be dedicated hosts.

To create new 1.22 clusters, you need to add the ec2:GetConsoleOutput permission to your Anthos Multi-Cloud API role.

A security vulnerability, CVE-2022-0847, has been discovered in the Linux kernel version 5.8 and later that can potentially escalate container privileges to root. This vulnerability affects Anthos Clusters on AWS running Kubernetes version 1.21 on Ubuntu.

For more information, see the GCP-2022-012 security bulletin.

A security vulnerability, CVE-2022-23648, has been discovered in containerd's handling of path traversal in the OCI image volume specification. Containers launched through containerd's CRI implementation with a specially-crafted image configuration could gain full read access to arbitrary files and directories on the host.

For more information, see the GCP-2022-013 security bulletin.

Anthos Clusters on AWS now sets the default instance type to m5.large when you create a new cluster or node pool. The previous default instance type was t3.medium.

March 21, 2022

Anthos clusters on AWS now supports clusters in the ap-southeast-2 region. For more information, see Supported regions.

February 22, 2022

Kubernetes version 1.21.6-gke.1500 is now available. For more information, see the Kubernetes OSS release notes.

You can now launch clusters in the ap-northeast1 and sa-east-1 AWS regions.

Fixed CVE-2021-4154, see GCP-2022-002 for more details.

Fixed CVE-2022-0185, see GCP-2022-002 for more details.

February 04, 2022

A security vulnerability, CVE-2021-4034, has been discovered in pkexec, a part of the Linux policy kit package (polkit), that allows an authenticated user to perform a privilege escalation attack. PolicyKit is generally used only on Linux desktop systems to allow non-root users to perform actions such as rebooting the system, installing packages, restarting services etc, as governed by a policy.

Anthos clusters on AWS is unaffected.

For instructions and more details, see the GCP-2022-004 security bulletin

December 02, 2021

Anthos on AWS is now generally available through the Multi-Cloud API.

With the latest release, we've simplified installation and streamlined our cluster management technology. You can now use a single API for full lifecycle management of Anthos clusters running in AWS or Azure. This release introduces gcloud command groups for deploying Anthos clusters in AWS, Azure, and Google Cloud. Clusters you create in other clouds appear in the Google Cloud Console, creating a centralized management view complete with cluster telemetry and logging.

The Multi-Cloud API authenticates with each cloud using a service account or application registration, and allows clusters to be deployed on existing or newly created VPCs. It supports multiple instance types in each cloud across multiple regions. As a reminder, Anthos clusters on Azure or AWS integrate with each respective cloud's KMS, storage facilities, and load balancing.

Anthos on AWS is available today, with either subscription or pay-as-you-go pricing.

You can now create, update, and delete clusters on AWS with the gcloud tool. Read more about our Multi-Cloud API.

Automatic Container monitoring and system logging with Cloud Logging and Cloud Monitoring.

You can now authenticate for cluster management functions with Google Cloud identities.

Clusters now use Dataplane V2 by default.

Clusters now use Workload Identity by default.