Connect Agent

Related topics

• Connect Agent depends on Connect API From the official documentation: “This agent connects back to the Connect API service on Google Cloud to create a secure link to Google Cloud.”
• Connect Agent is part of GKE attached clusters From the official documentation: “GKE attached clusters deploys a workload called the Connect Agent in your cluster.”
• Connect gateway depends on Connect Agent From the official documentation: “You need at least one node pool to use Connect gateway because it relies on the Connect agent, which runs as a Deployment in the cluster.”
• cluster works with Connect Agent From the official documentation: “Running the `bmctl` command starts setting up a new hybrid cluster. This includes doing preflight checks on the nodes, creating the admin and user clusters and also registering the cluster with Google Cloud using [Connect…”
• Connect Agent works with Prometheus From the official documentation: “Prometheus collects useful metrics from Connect Agent, like errors connecting to Google and the number of open connections.”
• Cloud Monitoring works with Cloud Service Mesh From the official documentation: “Cloud Service Mesh integrates with Cloud Logging and Cloud Monitoring.”
• Cloud Service Mesh works with Prometheus From the official documentation: “By default environments that install Cloud Service Mesh with Istio CA report metrics to Prometheus.”
• Cloud Monitoring works with Config Sync From the official documentation: “Config Sync supports exporting metrics to Cloud Monitoring only from GKE clusters.”
• 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 Monitoring works with Google Distributed Cloud connected From the official documentation: “- Manage Distributed Cloud connected logs and metrics in Cloud Monitoring.”
• Cloud Service Mesh depends on Cloud Monitoring From the official documentation: “Cloud Service Mesh uses Cloud Monitoring to provide automatic telemetry and logs.”
• Google Distributed Cloud connected works with Prometheus From the official documentation: “Distributed Cloud connected supports the [Prometheus](https://prometheus.io) metrics solution for collecting metrics on your Distributed Cloud connected workloads.”
• node pool is part of cluster From the official documentation: “Node pools are created and populated automatically when you create a cluster.”
• Cloud Monitoring works with Google Cloud Managed Service for Prometheus From the official documentation: “Managed Service for Prometheus shares the data-storage backend, Monarch, with Cloud Monitoring.”
• Cloud Monitoring works with Prometheus From the official documentation: “When you configure Prometheus with [Stackdriver Prometheus sidecar (deprecated)](https://github.com/Stackdriver/stackdriver-prometheus-sidecar), metrics exported by Prometheus are converted to Cloud Monitoring metric types with simple [metric…”
• Cloud Monitoring is an alternative to Prometheus From the official documentation: “Configure your own alerting policies in Cloud Monitoring or in Prometheus for issues affecting your workloads or local environment.”
• Cloud Service Mesh is part of cluster From the official documentation: “- **Canary cluster migration**: In this strategy, you create a new cluster and then provision managed Cloud Service Mesh on it.”
• 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”
• Cloud Service Mesh works with Google Cloud Managed Service for Prometheus From the official documentation: “| Google Cloud Managed Service for Prometheus, not including the Cloud Service Mesh dashboard | \* | \* |”
• Config Sync configures cluster From the official documentation: “To read and apply a config to a cluster to create or configure a Kubernetes object or resource in that cluster, GDC uses Config Sync.”
• Config Sync works with GKE attached clusters From the official documentation: “GKE attached clusters lets you view your existing Kubernetes clusters in the Google Cloud console along with your GKE clusters, and enable several GKE features on them, including centralized configuration control with Config Sync.”
• Config Sync works with Google Cloud Managed Service for Prometheus From the official documentation: “Config Sync metrics use [Google Cloud Managed Service for Prometheus](/stackdriver/docs/managed-prometheus) to load metrics into Cloud Monitoring.”
• Connect gateway works with Google Distributed Cloud connected From the official documentation: “`connectgateway.googleapis.com`: provides a secure connection between the Config Delivery service and your Distributed Cloud connected clusters”
• Connect gateway depends on node pool From the official documentation: “You need at least one node pool to use Connect gateway because it relies on the Connect agent, which runs as a Deployment in the cluster.”
• GKE attached clusters works with Google Cloud Managed Service for Prometheus From the official documentation: “This page explains how you can set up managed data collection with [Google Cloud Managed Service for Prometheus](/stackdriver/docs/managed-prometheus) for GKE attached clusters.”
• Google Cloud Managed Service for Prometheus is part of Cloud Monitoring From the official documentation: “Google Cloud Managed Service for Prometheus is part of Cloud Monitoring and is available as an option for system components.”
• Google Cloud Managed Service for Prometheus works with Prometheus From the official documentation: “[Google Cloud Managed Service for Prometheus](/stackdriver/docs/managed-prometheus) describes how to collect Prometheus metrics from applications running on Google Kubernetes Engine and Kubernetes.”