Infra Manager

Related topics

• Cloud Build works with Infra Manager From the official documentation: “Infra Manager uses the first connection where the Cloud Build repository URL matches the Terraform configuration (referenced in `--git-source-repo`), and where it is able to generate a read-only token.”
• Infra Manager works with Terraform From the official documentation: “Infra Manager automates the deployment and management of Google Cloud infrastructure resources using Terraform.”
• Cloud SQL works with Compute Engine From the official documentation: “Cloud SQL uses Compute Engine virtual machines (VMs) with persistent storage disks.”
• 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.”
• Cloud SQL works with GKE From the official documentation: “The app uses Cloud SQL, Vertex AI, and either Google Kubernetes Engine (GKE) or Cloud Run.”
• 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.”
• Infrastructure Manager depends on Cloud Build From the official documentation: “Infra Manager uses Cloud Build to create and update deployments.”
• Terraform configures Compute Engine From the official documentation: “Provisioning Compute Engine virtual machines (VMs) with Terraform lets you evaluate Google Distributed Cloud in high availability (HA) mode without physical hardware.”
• Cloud Build works with Cloud SQL From the official documentation: “This page contains information and examples for connecting to a Cloud SQL instance from a service running in Cloud Build.”
• Cloud Build 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.”
• 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.”
• 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 SQL works with Secret Manager From the official documentation: “This page describes four use cases for using Secret Manager to manage secrets with Cloud SQL:”
• GKE works with Google Cloud CLI From the official documentation: “GKE manages end-user authentication for you through the Google Cloud CLI.”
• Infrastructure Manager works with Terraform From the official documentation: “Learn more about [Terraform with Infra Manager](/infrastructure-manager/docs/infra-manager-terraform).”
• Secret Manager secures Cloud SQL From the official documentation: “Secret Manager provides centralized and secure storage of sensitive data such as Cloud SQL configuration.”
• 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 Infrastructure Manager From the official documentation: “If you are using a private Git repository, ensure that you have connected to [your GitHub host](/build/docs/automating-builds/github/connect-repo-github?generation=2nd-gen#gcloud) and [GitHub…”
• Cloud Build works with Terraform From the official documentation: “You have successfully configured data quality rules that are managed using Terraform and Cloud Build.”
• Cloud SQL depends on Compute Engine From the official documentation: “Cloud SQL uses Compute Engine virtual machines (VMs) with persistent storage disks.”
• Cloud SQL works with Terraform From the official documentation: “For more information about using Cloud SQL with Terraform, see [Cloud SQL Database Instance](https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/sql_database_instance) in the Terraform documentation.”
• GKE works with Terraform From the official documentation: “Terraform is a popular open source IaC tool created by HashiCorp that supports a wide range of Cloud services, including GKE.”
• 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.”
• Google Cloud CLI works with Infrastructure Manager From the official documentation: “When you use the [gcloud CLI](/sdk/gcloud/reference/infra-manager) to access Infra Manager, you authenticate to Google Cloud as a principal, which provides the credentials used by the gcloud CLI commands.”
• Google Cloud CLI is an alternative to Terraform From the official documentation: “You can create an Eventarc trigger with a deployed workflow as the event receiver by using the Google Cloud CLI (`gcloud` or Terraform), or through the Google Cloud console.”
• Secret Manager works with Terraform From the official documentation: “- Secret Manager: You can store and retrieve the secret using Secret Manager. To learn how to use Secret Manager with Terraform, see [google_secret_manager_secret](https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/secret_manager_secret.html).”
• Terraform depends on Google Cloud CLI From the official documentation: “Terraform support for agent policies is built on top of the Google Cloud CLI commands.”