GKE Enterprise Policy Controller

Related topics

• Cloud Service Mesh works with GKE Enterprise Policy Controller From the official documentation: “In the following sections, you leverage [Policy Controller](/anthos-config-management/docs/concepts/policy-controller) to enforce policies from the [Cloud Service Mesh policy bundle](/anthos-config-management/docs/how-to/using-asm-security-policy) by [creating…”
• Config Connector works with GKE Enterprise Policy Controller From the official documentation: “Use Policy Controller to create policies that govern how users can create Google Cloud resources with Config Connector.”
• GKE Enterprise Policy Controller secures Cloud Service Mesh From the official documentation: “[GKE Enterprise Policy Controller](https://cloud.google.com/anthos-config-management/docs/concepts/policy-controller) validates and audits policy configurations in the mesh to prevent misconfigurations.”
• 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.”
• Identity and Access Management works with Workload Identity Federation for GKE From the official documentation: “Instead, your GKE cluster directly authenticates workloads using Google Cloud IAM.”
• 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 depends on Workload Identity From the official documentation: “Cloud Service Mesh uses Workload Identity to provide secure access to required Google APIs and resources.”
• Cloud Service Mesh works with Workload Identity Federation for GKE From the official documentation: “When Envoy (`envoy-proxy`) connects to Cloud Service Mesh to fetch the xDS configuration, it uses Workload Identity Federation for GKE and the Compute Engine VM default service account (unless the bootstrap was changed).”
• Identity and Access Management secures Compute Engine From the official documentation: “Compute Engine uses Identity and Access Management (IAM) for authorization.”
• Identity and Access Management works with Workload Identity From the official documentation: “Using [Workload Identity](/kubernetes-engine/docs/how-to/workload-identity) is the recommended way to allow GKE workloads to authenticate with Google APIs and for administrators to apply "least privilege" authorization controls using IAM.”
• Cloud Service Mesh works with Identity and Access Management From the official documentation: “For information about how and which permissions are evaluated for each method, see the Identity and Access Management documentation for Cloud Service Mesh.”
• Cloud Service Mesh depends on Kubernetes From the official documentation: “Cloud Service Mesh builds upon the underlying platform (for example, Kubernetes). Thus, Cloud Service Mesh security is dependent upon the security of the underlying platform.”
• Cloud Service Mesh works with Kubernetes From the official documentation: “This service mesh architecture provides a control layer on top of Kubernetes.”
• Cloud Service Mesh depends on Workload Identity Federation for GKE From the official documentation: “Cloud Service Mesh requires Workload Identity Federation for GKE and is the recommended way to access Google APIs from GKE workloads.”
• Config Connector configures Compute Engine From the official documentation: “Config Connector deploys a running sample Compute Engine instance to your `PROJECT_ID` project.”
• Config Connector works with Identity and Access Management From the official documentation: “This document describes how to use Identity and Access Management to control how Config Connector can create and manage Google Cloud resources.”
• Config Connector works with Kubernetes From the official documentation: “#### [Config Connector](/config-connector/docs/overview) Configure Google Cloud services and resources using Kubernetes tooling and APIs.”
• Config Connector works with Prometheus From the official documentation: “You can use [Prometheus](https://prometheus.io/) to collect and show metrics from Config Connector.”
• Config Connector depends on Workload Identity From the official documentation: “Create or identify a GKE cluster where Config Connector has not yet been installed and that has [Workload Identity](/kubernetes-engine/docs/how-to/workload-identity#enable_on_new_cluster) and [Kubernetes Engine Monitoring](/monitoring/kubernetes-engine/installing) enabled.”
• Config Connector works with Workload Identity From the official documentation: “Setup Workload Identity if installing Config Connector for the first time.”
• Config Connector depends on Workload Identity Federation for GKE From the official documentation: “Config Connector creates and manages Google Cloud resources by authenticating with an Identity and Access Management (IAM) service account and using Workload Identity Federation for GKE to bind IAM service accounts with Kubernetes service accounts.”
• Identity and Access Management secures Cloud Service Mesh From the official documentation: “Access to Cloud Service Mesh in the Google Cloud console is controlled by [Identity and Access Management (IAM)](/iam/docs/overview).”
• Kubernetes works with Prometheus From the official documentation: “Metrics whose names begin `external.googleapis.com/prometheus/` come from [Prometheus](https://prometheus.io/), an open-source monitoring tool often used with Kubernetes.”