target

Related topics

• canary deployment strategy configures target From the official documentation: “The pipeline will deploy to two targets: `dev` and `staging`. And the `staging` target uses a [canary deployment strategy](/deploy/docs/deployment-strategies/canary).”
• Cloud Run works with target From the official documentation: “You now have a pipeline, with one multi-target comprising two GKE or Cloud Run targets, ready to deploy your application.”
• GKE works with target From the official documentation: “You now have a pipeline, with one multi-target comprising two GKE or Cloud Run targets, ready to deploy your application.”
• GKE attached clusters works with target From the official documentation: “The target can point to [GKE](/deploy/docs/config-files#for_gke_targets), [GKE attached clusters](/deploy/docs/config-files#for_anthos_targets), [Cloud Run](/deploy/docs/config-files#for_run_targets), or [custom targets](/deploy/docs/deploy-to-custom-targets).”
• target is part of Cloud Deploy From the official documentation: “Create and manage Target resources for Cloud Deploy.”
• target is part of delivery pipeline From the official documentation: “If you change a delivery pipeline, or any of its targets, after a release is created, you can do the following:”
• 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 Deploy works with Cloud Run From the official documentation: “Quickstart: Deploy an app to Cloud Run by using Cloud Deploy”
• Cloud Logging works with GKE From the official documentation: “Enable Cloud Logging on GKE Clusters”
• Cloud Monitoring works with Cloud Service Mesh From the official documentation: “Cloud Service Mesh integrates with Cloud Logging and Cloud Monitoring.”
• Cloud Monitoring works with GKE From the official documentation: “Enable Cloud Monitoring on GKE Clusters”
• Cloud Service Mesh works with GKE From the official documentation: “# Set up a proxyless gRPC service mesh on GKE”
• Cloud Logging works with Cloud Service Mesh From the official documentation: “Cloud Service Mesh integrates with Cloud Logging and Cloud Monitoring.”
• 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 Logging works with Pub/Sub From the official documentation: “Pub/Sub writes various log entries to Cloud Logging in the Google Cloud console.”
• Cloud Service Mesh depends on GKE From the official documentation: “Provision managed Cloud Service Mesh on a GKE cluster.”
• Cloud Build works with Cloud Run From the official documentation: “Cloud Build - create container images and deploy to Cloud Run.”
• Cloud Logging works with Cloud Monitoring From the official documentation: “You can store and view query-response activity logs in Cloud Logging and set up logs-based monitoring by using Cloud Monitoring.”
• Binary Authorization works with GKE From the official documentation: “Now, you create a GKE cluster with Binary Authorization enabled.”
• Cloud Build works with Cloud Deploy From the official documentation: “The pipeline uses Cloud Build for CI and Cloud Deploy for CD.”
• Cloud Monitoring works with GKE attached clusters From the official documentation: “GKE attached clusters has built-in integration with Cloud Monitoring for system metrics of nodes, pods, and containers.”
• 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 Service Mesh depends on Cloud Monitoring From the official documentation: “Cloud Service Mesh uses Cloud Monitoring to provide automatic telemetry and logs.”
• 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 Build works with GKE From the official documentation: “Remove the permission granted to Cloud Build to connect to GKE.”
• Cloud Deploy works with GKE From the official documentation: “Quickstart: Deploy an app to GKE by using Cloud Deploy”
• Cloud Deploy depends on Pub/Sub From the official documentation: “Cloud Deploy uses Pub/Sub to publish notifications for two purposes:”
• Cloud Deploy works with Pub/Sub From the official documentation: “Cloud Deploy publishes operational messages to Pub/Sub.”
• Cloud Logging works with GKE attached clusters From the official documentation: “This document describes how GKE attached clusters integrates with Cloud Logging and shows you how to access your logs.”
• Cloud Monitoring works with Cloud Run From the official documentation: “Cloud Monitoring records metrics regarding the execution of Cloud Run.”
• Cloud Monitoring works with Pub/Sub From the official documentation: “Use Cloud Monitoring and Pub/Sub to set up custom monitoring and alerting policies for exported 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.”
• 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.”
• 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 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 GKE attached clusters From the official documentation: “To enable Binary Authorization for GKE attached clusters, perform the following steps:”
• Cloud Build works with Cloud Logging From the official documentation: “- [`roles/logging.logWriter`](/iam/docs/roles-permissions/logging)— Required to store build logs in Cloud Logging.”
• 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 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 Deploy depends on Cloud Build From the official documentation: “Cloud Deploy calls Cloud Build to render your manifests and to deploy to the target runtime.”
• Cloud Deploy works with Cloud Logging From the official documentation: “Cloud Deploy and its dependent services publish logs to Cloud Logging, part of Google Cloud Observability.”
• Cloud Deploy works with GKE attached clusters From the official documentation: “This document describes how to configure and use canary deployments to deploy your applications to GKE or GKE attached clusters using Cloud Deploy with service-based networking.”
• Cloud Logging is an alternative to Cloud Monitoring From the official documentation: “To see the status of your invalidation request or find a definitive list of recently submitted requests, you can use Cloud Logging or Cloud Monitoring.”
• Cloud Logging works with Cloud Run From the official documentation: “Cloud Logging captures, stores, and analyzes Cloud Run logs.”
• Cloud Service Mesh works with GKE attached clusters From the official documentation: “GKE attached clusters - Third-party Kubernetes clusters that have been registered to a fleet. Cloud Service Mesh is supported on the following cluster types: - Amazon EKS clusters - Microsoft AKS clusters”
• delivery pipeline is part of Cloud Deploy From the official documentation: “Delivery Pipeline being managed by Cloud Deploy.”