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).”
• certificate-bound tokens works with Google Kubernetes Engine (GKE) From the official documentation: “This requirement helps ensure that only the intended, trusted runtime environment, such as a Cloud Run container or a Google Kubernetes Engine (GKE) Pod, can use the certificate-bound tokens.”
• 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.”
• labels configures Google Kubernetes Engine (GKE) From the official documentation: “To register agents deployed on [Google Kubernetes Engine (GKE)](/kubernetes-engine/docs/tutorials/agentic-adk-vertex), add the required Kubernetes [labels](https://kubernetes.io/docs/concepts/overview/working-with-objects/labels/) and…”
• Artifact Registry works with Cloud Build From the official documentation: “1. Builds your container and pushes it to Artifact Registry.”
• Artifact Analysis works with Artifact Registry From the official documentation: “Artifact Analysis scans new images when they're uploaded to Artifact Registry.”
• Artifact Registry works with Cloud Run From the official documentation: “Cloud Run recommends using Artifact Registry.”
• Binary Authorization secures Cloud Run From the official documentation: “Binary Authorization is a software supply chain security product for GKE and Cloud Run.”
• Cloud Build works with Cloud Run From the official documentation: “Cloud Build - create container images and deploy to Cloud Run.”
• Artifact Registry works with Google Kubernetes Engine From the official documentation: “You can identify frequently pulled images and copy them to Artifact Registry for deployments to Google Cloud environments such as Google Kubernetes Engine or Cloud Run.”
• Binary Authorization works with GKE From the official documentation: “Now, you create a GKE cluster with Binary Authorization enabled.”
• 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.”
• Artifact Analysis works with Binary Authorization From the official documentation: “With Binary Authorization, you may use Artifact Analysis to store attestors and attestations as notes and occurrences, respectively.”
• Artifact Analysis works with Cloud Build From the official documentation: “Cloud Build generates this metadata and Artifact Analysis stores the information if you use Cloud Build to build the image.”
• Artifact Analysis secures Cloud Run From the official documentation: “To identify and mitigate security risks in the container images, use Artifact Analysis to automatically run vulnerability scans.”
• Artifact Registry works with GKE From the official documentation: “In the next tutorial, you deploy those images from the Artifact Registry repository to a GKE cluster:”
• Binary Authorization works with Cloud Run From the official documentation: “This guide shows you how to disable Binary Authorization for Cloud Run.”
• Cloud Build works with GKE From the official documentation: “Remove the permission granted to Cloud Build to connect to GKE.”
• 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.”
• Google Kubernetes Engine depends on BigQuery From the official documentation: “This happens because Google Kubernetes Engine depends on BigQuery and Managed Service for Apache Airflow inherits this dependency from the Kubernetes Engine API.”
• labels is part of BigQuery From the official documentation: “BigQuery supports adding labels to resources.”
• Artifact Analysis secures Artifact Registry From the official documentation: “Turn on Artifact Analysis, which allows for security scanning, for your Artifact Registry repository.”
• Artifact Registry secures Cloud Run From the official documentation: “You can use Artifact Registry together with other Google Cloud products and features to improve the security posture of developer workflows and tools, software dependencies, CI/CD systems used to build and deploy your software, and runtime environments such as Google Kubernetes…”
• Artifact Registry secures Google Kubernetes Engine From the official documentation: “You can use Artifact Registry together with other Google Cloud products and features to improve the security posture of developer workflows and tools, software dependencies, CI/CD systems used to build and deploy your software, and runtime environments such as Google Kubernetes…”
• BigQuery works with Cloud Run From the official documentation: “You can then use Cloud Run to transcode data present in the bucket and move it to BigQuery.”
• BigQuery works with GKE From the official documentation: “Subsequently, by integrating BigQuery with GKE, you can use BigQuery to efficiently handle massive datasets (like Google Analytics) and the model's natural language understanding capabilities to generate meaningful insights.”
• BigQuery works with labels From the official documentation: “Labels are exported to BigQuery with the corresponding Google Cloud resources and their usage.”
• Binary Authorization secures Artifact Registry From the official documentation: “If you're using Artifact Registry to store your artifacts, we recommend that you configure controls to help you secure your artifact repositories, such as access control, data exfiltration prevention, vulnerability scanning, and Binary Authorization.”
• Binary Authorization works with Cloud Build From the official documentation: “Cloud Build, which produces attestations and provenance that Binary Authorization can use for enforcement and monitoring.”
• 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.”
• certificate-bound tokens works with Cloud Run From the official documentation: “This requirement helps ensure that only the intended, trusted runtime environment, such as a Cloud Run container or a Google Kubernetes Engine (GKE) Pod, can use the certificate-bound tokens.”
• Cloud Build depends on GKE From the official documentation: “To deploy the application in your Kubernetes cluster, Cloud Build needs the Kubernetes Engine Developer [Identity and Access Management Role](/iam/docs/understanding-roles).”
• Cloud Build works with Google Kubernetes Engine From the official documentation: “This tutorial shows you how to validate configs with [Cloud Build](/build) when using Google Kubernetes Engine clusters.”
• Cloud Run depends on Artifact Registry From the official documentation: “The containerized function is stored in Artifact Registry and deployed to Cloud Run as a service.”
• 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.”
• GKE depends on Artifact Registry From the official documentation: “When you create or update a cluster, GKE pulls container images for the Kubernetes system software running on the control plane and nodes from Artifact Registry repositories in the `pkg.dev` or the `gcr.io` domain.”