GKE attached clusters release notes

1.28.0-gke.1

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

• No longer need to add any bindings for gke-system/gke-telemetry-agent when creating a cluster.
• 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.
• No longer need to add any bindings for gke-system/binauthz-agent when enabling binary authorization.

1.25.0-gke.8, 1.26.0-gke.6, and 1.27.0-gke.3

Added support for attaching any CNCF-conformant Kubernetes cluster, in addition to EKS and AKS clusters. To attach a cluster, specify the distribution type as "generic".

1.27.0-gke.1

• 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 the authorization.admin_groups field. This allows users to specify Google groups as cluster-admins through the management plane.

• 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.

• Added proxy support for attaching AKS/EKS clusters. For details, see Connect to your EKS cluster and Connect to your AKS cluster.

Added support for managing Anthos attached clusters in the Google Cloud console. You can now use a user-friendly graphical interface to manage your Amazon Elastic Kubernetes Service (EKS) and Azure Kubernetes Service (AKS) clusters on the Anthos platform. Using the Google Cloud console, you can view cluster status, update attached cluster components, and detach clusters.

For more information, including instructions, see the following documentation:

• View the status of your EKS attached cluster
• Update your EKS attached cluster
• Detach your EKS attached cluster
• View the status of your AKS attached cluster
• Update your AKS attached cluster
• Detach your AKS attached cluster

• You can now view, update, and delete attached clusters via the Google Cloud console. For details, see the how-to guides for EKS and AKS.
• Starting with 1.26 clusters, customers can configure access to clusters for Google groups rather than access per user. For details, see Connect to your EKS attached cluster or Connect to your AKS attached cluster.
• 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. (This feature is available for 1.25.0-gke.3 and 1.26.0-gke.1).

This release includes the following Anthos attached clusters platform versions:

• 1.21.0-gke.1
• 1.22.0-gke.1
• 1.23.0-gke.3
• 1.24.0-gke.2
• 1.25.0-gke.2

This release of Anthos attached clusters supports AKS and EKS cluster versions 1.21, 1.22, 1.23, 1.24 and 1.25.

This generation of Anthos attached clusters further streamlines the process of attaching your cluster to the Google Cloud infrastructure.

This release supports logging and monitoring of your cluster's status with full log examination through Google's Cloud Logging UI.

This release supports migration of your existing EKS and AKS clusters from the previous generation Anthos attached clusters product.