Google Kubernetes Engine (GKE)

Related topics

• Binary Authorization works with Google Kubernetes Engine (GKE) From the official documentation: “If you use Google Kubernetes Engine (GKE) or Cloud Run, you can establish an approval process by using [Binary Authorization](/binary-authorization/docs/overview).”
• Cloud Run is an alternative to Google Kubernetes Engine (GKE) From the official documentation: “The architecture shows [Cloud Run](/run/docs/configuring/services/gpu-best-practices) and [GKE](/kubernetes-engine/docs/concepts/machine-learning/inference) as alternative runtimes for the AI model that you choose to use.”
• Cluster Autoscaler is part of Google Kubernetes Engine (GKE) From the official documentation: “- Automatically adjust the size of GKE clusters based on the current load by using [cluster autoscaler](/kubernetes-engine/docs/concepts/cluster-autoscaler).”
• GKE Autopilot is part of Google Kubernetes Engine (GKE) From the official documentation: “- Use [GKE Autopilot](/kubernetes-engine/docs/concepts/autopilot-overview) to take advantage of cost-optimization techniques like bin packing and autoscaling that GKE implements by default.”
• Google Kubernetes Engine (GKE) works with Web Security Scanner From the official documentation: “Use [Web Security Scanner](/security-command-center/docs/concepts-web-security-scanner-overview) to help identify security vulnerabilities in your App Engine, Compute Engine, and GKE web applications.”
• Google Kubernetes Engine (GKE) works with Workload Identity Federation From the official documentation: “- Use [Workload Identity Federation](/iam/docs/workload-identities) for applications that run on GKE or run outside Google Cloud to access resources securely.”
• Cloud Run depends on Pub/Sub From the official documentation: “Cloud Run function triggered by Pub/Sub to fetch HYPR MFA logs and write to GCS.”
• Cloud Service Mesh works with GKE From the official documentation: “# Set up a proxyless gRPC service mesh on GKE”
• Cloud Run works with Cloud Service Mesh From the official documentation: “This section shows you how to troubleshoot common errors with Cloud Service Mesh and Cloud Run.”
• Binary Authorization secures Cloud Run From the official documentation: “Binary Authorization is a software supply chain security product for GKE and Cloud Run.”
• Cloud Service Mesh depends on GKE From the official documentation: “Provision managed Cloud Service Mesh on a GKE cluster.”
• Cloud Storage is an alternative to Pub/Sub From the official documentation: “To keep audit logs for a longer period of time or to use more powerful search capabilities, you can route copies of your audit logs to Cloud Storage, BigQuery, or Pub/Sub.”
• Cloud Audit Logs works with Cloud Storage From the official documentation: “This page provides supplemental information for using [Cloud Audit Logs](/logging/docs/audit) with Cloud Storage.”
• Cloud Storage works with Pub/Sub From the official documentation: “| **Google Cloud** | Cloud Storage | Pub/Sub |”
• Binary Authorization works with GKE From the official documentation: “Now, you create a GKE cluster with Binary Authorization enabled.”
• Cloud Run works with Cloud Storage From the official documentation: “Receive events from Cloud Storage in a Cloud Run service”
• Cloud Run is an alternative to GKE From the official documentation: “For your containerized websites, you can also deploy them to [Cloud Run](/run) in addition to [using GKE](#kubernetes-engine).”
• Cloud Run works with Google Kubernetes Engine From the official documentation: “Connecting Cloud Run services to Cloud Service Mesh lets you securely route traffic to workloads on GKE.”
• GKE works with Workload Identity Federation From the official documentation: “To allow GitHub Actions authenticate Google Cloud and deploy to GKE, use [workload identity federation](/iam/docs/workload-identity-federation).”
• Binary Authorization works with Cloud Run From the official documentation: “This guide shows you how to disable Binary Authorization for Cloud Run.”
• Binary Authorization secures Cloud Service Mesh From the official documentation: “[Google Cloud Binary Authorization](/binary-authorization) ensures that the workload images in the mesh are the ones authorized by the administrators.”
• Cloud Audit Logs works with Pub/Sub From the official documentation: “Working with audit logs Learn about the default and optional logs created by Pub/Sub as part of Cloud Audit Logs”
• Cloud Run works with GKE From the official documentation: “Leverage Google Kubernetes Engine (GKE) and Cloud Run to deploy applications to the Google Cloud, optimizing costs, performance, and management overhead.”
• Cloud Run works with Pub/Sub From the official documentation: “A Cloud Run app receives the Pub/Sub message.”
• Cloud Service Mesh works with Google Kubernetes Engine From the official documentation: “A GKE Cluster with Cloud Service Mesh enabled”
• Cluster Autoscaler is part of GKE From the official documentation: “GKE's *cluster autoscaler* automatically resizes the number of nodes in a given node pool, based on the demands of your workloads.”
• Cluster Autoscaler is part of Google Kubernetes Engine From the official documentation: “Google Kubernetes Engine: [Cluster autoscaler](/kubernetes-engine/docs/concepts/cluster-autoscaler) and [node auto-provisioning](/kubernetes-engine/docs/how-to/node-auto-provisioning)”
• GKE works with Pub/Sub From the official documentation: “GKE publishes upgrade notifications to [Pub/Sub](/pubsub/docs/overview), providing you with a channel to receive information from GKE about your clusters.”
• GKE Autopilot is part of GKE From the official documentation: “You can configure KubeRay on TPUs in a GKE Autopilot or Standard cluster.”
• Web Security Scanner secures GKE From the official documentation: “Web Security Scanner identifies security vulnerabilities and misconfigurations in your App Engine, Google Kubernetes Engine (GKE), and Compute Engine web applications.”
• Binary Authorization works with Cloud Audit Logs From the official documentation: “This guide shows you how to view Binary Authorization for Cloud Run in Cloud Audit Logs.”
• Binary Authorization works with Cloud Service Mesh From the official documentation: “Cloud Service Mesh users need to only set up the Binary Authorization policy.”
• Binary Authorization secures GKE From the official documentation: “Use Binary Authorization to make sure trusted images are deployed to Google Kubernetes Engine (GKE) and Cloud Run.”
• Binary Authorization works with Google Kubernetes Engine From the official documentation: “Using Binary Authorization on Google Kubernetes Engine ensures that the MLLP adapter can only be deployed from a verified and signed container image.”
• Binary Authorization secures Google Kubernetes Engine From the official documentation: “Use Binary Authorization to make sure trusted images are deployed to Google Kubernetes Engine (GKE) and Cloud Run.”
• Cloud Audit Logs works with Cloud Run From the official documentation: “The sample code shows you how to read Cloud Storage events using Cloud Audit Logs in a service deployed to Cloud Run.”
• Cloud Audit Logs works with Cloud Service Mesh From the official documentation: “This document describes the audit logs created by Cloud Service Mesh as part of [Cloud Audit Logs](/logging/docs/audit).”
• Cloud Audit Logs secures Cloud Service Mesh From the official documentation: “Cloud Audit Logs audits mesh operations.”
• Cloud Audit Logs works with Google Kubernetes Engine From the official documentation: “For clusters on patch versions 1.21.9 and 1.22.3 or later with Cloud Logging [enabled](/stackdriver/docs/solutions/gke/installing#installing), GKE provides a [Cloud Audit Logs log](/kubernetes-engine/docs/how-to/audit-logging#viewing_your_projects_admin_activity_log) to…”
• Cloud Audit Logs works with Web Security Scanner From the official documentation: “Cloud Audit Logs for Web Security Scanner let you track administrative and data-access operations on your resources to help you monitor access and configuration changes.”
• Cloud Run is an alternative to Google Kubernetes Engine From the official documentation: “**Agent and tool runtimes**: hosting and executing agents or MCP servers on runtimes such as Agent Runtime on Gemini Enterprise Agent Platform, Cloud Run, or Google Kubernetes Engine (GKE) incurs standard compute and runtime charges for those services.”
• Cloud Run works with Workload Identity Federation From the official documentation: “This tutorial describes how to use Workload Identity Federation to authenticate workloads that run outside of Google Cloud so that they can access microservices hosted by Cloud Run.”
• Cloud Service Mesh depends on Google Kubernetes Engine From the official documentation: “Cloud Service Mesh service security is supported only with GKE.”
• Cloud Service Mesh depends on Workload Identity Federation From the official documentation: “This error is shown if the GKE cluster does not have [Workload Identity Federation](/kubernetes-engine/docs/how-to/workload-identity) enabled on all node pools of that cluster, since this is a prerequisites for the installation of Cloud Service Mesh.”
• Cloud Storage works with GKE From the official documentation: “This example configures GKE to store Pod snapshots in the `FOLDER_PATH/` path inside the Cloud Storage bucket `BUCKET_NAME`:”
• Cloud Storage works with GKE Autopilot From the official documentation: “Both Cloud Run and GKE Autopilot let you connect with other services like Filestore and Cloud Storage buckets.”
• Cloud Storage works with Google Kubernetes Engine From the official documentation: “Often, media-related data residing in Cloud Storage is processed by applications running in Compute Engine or Google Kubernetes Engine, and the output of this process is written back to Cloud Storage.”
• Cluster Autoscaler works with Google Kubernetes Engine From the official documentation: “Configure the [cluster autoscaler](/kubernetes-engine/docs/concepts/cluster-autoscaler) and [node auto-provisioning](/kubernetes-engine/docs/how-to/node-auto-provisioning) to adjust the node count based on pending Pod resource requests like CPU, memory, GPU, and Cloud TPU.”
• GKE Autopilot depends on GKE From the official documentation: “GKE Autopilot is only supported with GKE version 1.21.3+.”
• Workload Identity Federation secures Cloud Storage From the official documentation: “To allow GKE to securely access the Cloud Storage bucket, set up GKE Workload Identity Federation:”
• Workload Identity Federation configures Pub/Sub From the official documentation: “If your architecture includes an [external identity provider](/iam/docs/workload-identity-federation#providers) such as Active Directory or a local Kubernetes cluster, you can use [workload identity federation](/iam/docs/workload-identity-federation) to manage access to Pub/Sub.”