Config Sync

Related topics

• Config Sync works with Kustomize From the official documentation: “Config Sync can automatically render Kustomize configurations that are stored in an unstructured source of truth.”
• Artifact Registry works with Config Sync From the official documentation: “Sync OCI artifacts from Artifact Registry”
• Cloud Monitoring works with Config Sync From the official documentation: “Config Sync supports exporting metrics to Cloud Monitoring only from GKE clusters.”
• Config Sync depends on fleet From the official documentation: “Config Sync requires that your clusters are registered to a fleet.”
• Config Sync works with GKE From the official documentation: “This quickstart shows you how to use Config Sync to implement a GitOps approach for managing your Google Kubernetes Engine clusters.”
• Config Sync works with Helm From the official documentation: “When you use Config Sync, the Kustomize configurations and Helm charts you place in your Git repository are automatically rendered.”
• Config Sync works with Policy Controller From the official documentation: “If you're using Policy Controller with Config Sync, you should be aware of the following interactions with resources stored in your source of truth, like a Git repository, that are synced by Config Sync:”
• Config Sync depends on Artifact Registry From the official documentation: “Config Sync needs read-only access to your OCI image stored in Artifact Registry so that it can read the configs included in the image and apply them to your clusters.”
• 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 custom metrics From the official documentation: “You can also export [custom metrics](https://github.com/GoogleContainerTools/config-sync/blob/main/docs/custom-metric-filter.md).”
• Config Sync depends on Git From the official documentation: “If you store your configs in Git, you must [grant Config Sync read-only access to Git](#git-creds-secret).”
• Config Sync works with Git From the official documentation: “Config Sync needs read-only access to your Git repository so that it can read the configs committed to the repository and apply them to your clusters.”
• Config Sync is part of GKE From the official documentation: “Config Sync and fleet team management features are available as part of GKE.”
• 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 CLI From the official documentation: “You can upgrade Config Sync using the Google Cloud console or the Google Cloud CLI.”
• Config Sync depends on Helm From the official documentation: “If you store your configs in [Helm](https://helm.sh/), you must [grant Config Sync read-only access to Helm](#helm-access).”
• Cloud Service Mesh depends on fleet From the official documentation: “All clusters in a particular Cloud Service Mesh must be registered to the same fleet.”
• Traffic Director is part of Cloud Service Mesh From the official documentation: “`TRAFFIC_DIRECTOR`: The core infrastructure of Google Cloud serves as the Cloud Service Mesh control plane.”
• 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.”
• 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 Service Mesh depends on GKE From the official documentation: “Provision managed Cloud Service Mesh on a GKE cluster.”
• Cloud Service Mesh works with Traffic Director From the official documentation: “**Note:** This is only applicable to Cloud Service Mesh with Traffic Director implementation.”
• GKE works with Traffic Director From the official documentation: “Provision managed Cloud Service Mesh on a GKE cluster.”
• Artifact Registry works with Cloud Run From the official documentation: “Cloud Run recommends using Artifact Registry.”
• 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.”
• Cloud Logging works with Compute Engine From the official documentation: “Compute Engine sends you Cloud Logging events for scheduled, started, or completed maintenance.”
• 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 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 Service Mesh depends on Cloud Monitoring From the official documentation: “Cloud Service Mesh uses Cloud Monitoring to provide automatic telemetry and logs.”
• 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.”
• fleet works with GKE From the official documentation: “Created a GKE cluster and registered it to a fleet”
• GKE depends on Compute Engine From the official documentation: “For example, GKE deploys clusters on Compute Engine VMs.”
• 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 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 Logging works with Google Kubernetes Engine From the official documentation: “By default, GKE clusters send system log data and system metric data to Logging and Monitoring.”
• Cloud Logging works with Traffic Director From the official documentation: “Cloud Service Mesh supports MeshConfig telemetry API to enable and disable Cloud Logging and Cloud Monitoring for GKE workloads.”
• Cloud Monitoring works with Cloud Run From the official documentation: “Cloud Monitoring records metrics regarding the execution of Cloud Run.”
• Cloud Monitoring works with Google Kubernetes Engine From the official documentation: “When Google Kubernetes Engine (GKE) [system metrics](/kubernetes-engine/docs/how-to/configure-metrics#system-metrics) are enabled, Cloud Monitoring collects the following metrics.”
• Cloud Monitoring works with Traffic Director From the official documentation: “Cloud Service Mesh supports MeshConfig telemetry API to enable and disable Cloud Logging and Cloud Monitoring for GKE workloads.”
• 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 Traffic Director From the official documentation: “This page provides a reference for the APIs that are used to configure Cloud Service Mesh for Cloud Run workloads.”
• Cloud Service Mesh works with Compute Engine From the official documentation: “Cloud Service Mesh supports a variety of infrastructures (GKE/Kubernetes, Compute Engine) and environments (on-premises, other clouds).”
• Cloud Service Mesh is part of fleet From the official documentation: “You can enable features such as Config Management and Cloud Service Mesh within your Fleet.”
• Cloud Service Mesh works with Google Kubernetes Engine From the official documentation: “A GKE Cluster with Cloud Service Mesh enabled”
• cluster works with Google Cloud CLI From the official documentation: “You can restore your backup to a new AlloyDB cluster using the Google Cloud console or Google Cloud CLI.”
• 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.”
• custom metrics is part of Cloud Monitoring From the official documentation: “Cloud Monitoring has a large number of built-in system metrics, but you can also create custom metrics.”
• GKE works with Google Cloud CLI From the official documentation: “GKE manages end-user authentication for you through the Google Cloud CLI.”
• Traffic Director depends on fleet From the official documentation: “All clusters in a particular Cloud Service Mesh must be registered to the same fleet.”
• Artifact Registry works with Cloud Logging From the official documentation: “Artifact Registry sends the following types of audit log data to Cloud Logging:”
• Artifact Registry works with Cloud Monitoring From the official documentation: “By default, Artifact Registry is configured to do the following: - Send system logs and audit logs to Cloud Logging - Send system metrics and resource metrics to Cloud Monitoring”
• 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 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.”