container image

Related topics

• Artifact Registry works with container image From the official documentation: “Cloud Build then automatically builds your code into a container image and pushes that image to an Artifact Registry [image registry](/run/docs/deploy-functions#image-repository).”
• Artifact Registry remote repository works with container image From the official documentation: “For higher availability, Google recommends deploying these Docker Hub or GitHub Container Registry images using an [Artifact Registry remote repository](/artifact-registry/docs/repositories/remote-repo).”
• Cloud Run works with container image From the official documentation: “**[Use the local configuration of an `app.yaml` file](#appyaml-config) (recommended)**: Choose this option to build a container image directly from your local source code and deploy it to Cloud Run.”
• container image is part of Artifact Registry From the official documentation: “While Cloud Run doesn't charge when a service isn't in use, you might still be [charged for storing the container image in Artifact Registry](https://cloud.google.com/artifact-registry/pricing).”
• container image depends on Artifact Registry From the official documentation: “You deploy a container image hosted in Artifact Registry.”
• Artifact Registry works with Cloud Build From the official documentation: “1. Builds your container and pushes it to Artifact Registry.”
• 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.”
• 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.”
• Pub/Sub works with Secret Manager From the official documentation: “Receive notifications via Pub/Sub when Secret Manager resources change.”
• Cloud Build works with Cloud Run From the official documentation: “Cloud Build - create container images and deploy to Cloud Run.”
• Customer-Managed Encryption Keys secures Pub/Sub From the official documentation: “Encrypt Pub/Sub topic with CMEK”
• 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 Secret Manager From the official documentation: “The secret is configured to be accessible by Cloud Run and Cloud Build.”
• 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.”
• Binary Authorization works with Cloud Run From the official documentation: “This guide shows you how to disable Binary Authorization for Cloud Run.”
• 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 Pub/Sub From the official documentation: “A Cloud Run app receives the Pub/Sub message.”
• Customer-Managed Encryption Keys secures Artifact Registry From the official documentation: “Artifact Registry also supports [organization policy constraints](/artifact-registry/docs/cmek#org-policy) that can require CMEK to protect resources.”
• Customer-Managed Encryption Keys works with Secret Manager From the official documentation: “In Secret Manager, you can use a CMEK to protect data at rest.”
• Customer-Managed Encryption Keys secures Secret Manager From the official documentation: “You can either create CMEKs manually to protect your Secret Manager resources or use Cloud KMS Autokey.”
• 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 works with Pub/Sub From the official documentation: “When you activate the Artifact Registry API in a Google Cloud project, Artifact Registry tries to automatically create a Pub/Sub topic with the topic ID `gcr` using Google-owned and Google-managed encryption keys.”
• 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.”
• Artifact Registry remote repository is part of Artifact Registry From the official documentation: “This page describes how to create Artifact Registry remote repositories.”
• Artifact Registry remote repository works with Secret Manager From the official documentation: “In this quickstart, you configure Docker Hub credentials in Secret Manager, create a remote repository, and pull a sample image.”
• 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.”
• Cloud Build works with Pub/Sub From the official documentation: “Cloud Build sends all build event updates, along with build metadata, [to Pub/Sub](/build/docs/subscribe-build-notifications) on either the `cloud-builds` topic or a user-defined topic.”
• 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.”
• Customer-Managed Encryption Keys secures Artifact Registry remote repository From the official documentation: “If you require customer-managed-encryption keys (CMEK) to encrypt repository content, then [create and enable](/artifact-registry/docs/cmek) a key in Cloud KMS for the repository.”
• Customer-Managed Encryption Keys secures Cloud Run From the official documentation: “If you want to control your encryption keys, then you can use customer-managed encryption keys (CMEKs) in [Cloud KMS](/kms/docs) with CMEK-integrated services including Cloud Run.”
• Secret Manager secures Cloud Run From the official documentation: “Store sensitive credentials in Secret Manager for secure access by the Cloud Run function.”