Image Builder

Related topics

• Artifact Registry works with Image Builder From the official documentation: “When you configure an Artifact Registry destination, Image Builder performs the following steps:”
• Cloud Build works with Image Builder From the official documentation: “Image Builder outputs the test outcomes in a standard JUnit XML format directly to the Cloud Build logs.”
• Compute Engine works with Image Builder From the official documentation: “// submitBuild submits a Cloud Build build that uses Image Builder to // customize, validate, and publish a VM image to Compute Engine and Artifact // Registry.”
• Image Builder depends on Cloud Build From the official documentation: “Image Builder requires that you enable the Compute Engine, Cloud Build, Artifact Registry, Service Usage, and Resource Manager APIs.”
• Image Builder depends on Compute Engine From the official documentation: “Image Builder requires that you enable the Compute Engine, Cloud Build, Artifact Registry, Service Usage, and Resource Manager APIs.”
• Artifact Registry works with Cloud Build From the official documentation: “1. Builds your container and pushes it to Artifact Registry.”
• Cloud Build works with Cloud Storage From the official documentation: “Cloud Build then stores Terraform files and the Terraform State File in a Cloud Storage bucket.”
• Cloud Storage works with Google Cloud CLI From the official documentation: “The gcloud CLI is the preferred command line tool for accessing Cloud Storage.”
• Compute Engine is an alternative to GKE From the official documentation: “You can also deploy a third-party model to either Vertex AI Model Garden or self-host on GKE or Compute Engine.”
• Artifact Registry works with Cloud Run From the official documentation: “Cloud Run recommends using Artifact Registry.”
• Cloud Build works with Cloud Run From the official documentation: “Cloud Build - create container images and deploy to Cloud Run.”
• Cloud Storage works with Compute Engine From the official documentation: “For example, you can create a service account that your Compute Engine instances use to access objects stored in Cloud Storage buckets.”
• Compute Engine works with Secret Manager From the official documentation: “To use Secret Manager with workloads running on Compute Engine or GKE, the underlying instance or node must have the `cloud-platform` OAuth scope.”
• 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.”
• Cloud Build works with Secret Manager From the official documentation: “The secret is configured to be accessible by Cloud Run and Cloud Build.”
• 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.”
• Cloud Run works with Secret Manager From the official documentation: “The secret is configured to be accessible by Cloud Run and Cloud Build.”
• Compute Engine works with Google Cloud CLI From the official documentation: “Some applications might use commands from the gcloud CLI, which is included by default in most Compute Engine images.”
• Compute Engine is an alternative to Google Kubernetes Engine From the official documentation: “You can install MongoDB on a Compute Engine instance or you can deploy MongoDB on Google Kubernetes Engine.”
• GKE depends on Compute Engine From the official documentation: “For example, GKE deploys clusters on Compute Engine VMs.”
• GKE works with Secret Manager From the official documentation: “To use Secret Manager with workloads running on Compute Engine or GKE, the underlying instance or node must have the `cloud-platform` OAuth scope.”
• 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:”
• Artifact Registry works with Google Cloud CLI From the official documentation: “Before you can push or pull images, configure Docker to use the Google Cloud CLI to authenticate requests to Artifact Registry.”
• Cloud Build works with GKE From the official documentation: “Remove the permission granted to Cloud Build to connect to GKE.”
• Cloud Build depends on Secret Manager From the official documentation: “Previously, for GitLab Enterprise and Bitbucket Data Center connections, when Secret Manager secrets were retrieved, permissions were checked against the Cloud Build service agent (P4SA) credentials only.”
• 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.”
• GKE works with Google Cloud CLI From the official documentation: “GKE manages end-user authentication for you through the Google Cloud CLI.”
• Google Kubernetes Engine works with Secret Manager From the official documentation: “To use Secret Manager with workloads running on Compute Engine or Google Kubernetes Engine, the underlying instance or node must have the `cloud-platform` OAuth scope.”
• 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 depends on Cloud Storage From the official documentation: “The registry service hosts your custom images in Cloud Storage under your Google Cloud project.”
• Artifact Registry works with Cloud Storage From the official documentation: “| Artifact Registry | Stored in Cloud Storage, for each data chunk | |”
• Artifact Registry works with Compute Engine From the official documentation: “Compute Engine can pull containers directly from Artifact Registry repositories so you can run containerized workloads on virtual machine (VM) instances.”
• 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…”
• Artifact Registry works with Secret Manager From the official documentation: “You can store an npm personal access token in Secret Manager and attach it to your remote repository so that Artifact Registry can authenticate upstream requests.”
• Cloud Build depends on Cloud Storage From the official documentation: “Cloud Build uses Cloud Storage to store build resources.”
• Cloud Build works with Compute Engine From the official documentation: “Automating builds on repository events ensures that Cloud Build immediately validates, builds, and publishes your custom OS images to Compute Engine and Artifact Registry upon code review or merge.”
• Cloud Build is an alternative to Compute Engine From the official documentation: “If Cloud Build is not available, use a small Compute Engine VM with a cron job to pull IOC data and write to GCS.”
• 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 Cloud CLI From the official documentation: “Use `gcloud` to submit the application source code to Cloud Build:”
• 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 works with Compute Engine From the official documentation: “This lets Cloud Run clients use this backend service route to send requests directly to Compute Engine instances.”
• Cloud Run works with Google Cloud CLI From the official documentation: “Google Cloud CLI contains a [local development environment](/sdk/gcloud/reference/beta/code/dev) for emulating Cloud Run that can build a container from source, run the container on your local machine, and automatically rebuild the container upon source code 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 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 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.”
• Compute Engine works with Google Kubernetes Engine From the official documentation: “Compute Engine integrates with Google Cloud technologies such as Cloud Storage, Google Kubernetes Engine, and BigQuery, to extend beyond the basic computational capability to create more complex and sophisticated applications.”
• 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.”
• Google Cloud CLI configures Compute Engine From the official documentation: “To replace a BYOL license with a PAYG license, use the Google Cloud CLI or the Compute Engine API.”
• Secret Manager secures Cloud Run From the official documentation: “Store sensitive credentials in Secret Manager for secure access by the Cloud Run function.”