Skip to main content

GKE Integration Overview

Updated over 2 weeks ago

Overview

Our platform offers a comprehensive analysis of Kubernetes spend and usage for both container and cloud infrastructure in GKE clusters. By continuously evaluating workload behavior and respective cloud infrastructure, we provide a 360° view of Kubernetes application costs. This unlocks deep analysis capabilities and opportunities for financial operations research.

Additionally, our DeepWaste Detection™ technology translates into actionable, cost-saving opportunities. Your team can leverage these insights for ongoing savings and improved efficiency.

Our technology addresses a wide spectrum of Kubernetes spend inefficiencies, from control-plane-related spend to workload and infrastructure rightsizing, storage, and network configuration. By leveraging native GCP capabilities we provide an integration that seamlessly fits into your existing setup without having to install a 3rd-party agent.

How it works

Networking

The integration starts by establishing a secure network connection between the PointFive platform and your GKE cluster.

For Public GKE clusters - we access them through their publicly available DNS endpoint.

For Private GKE clusters - we utilize the recommended GCP method - Using GKE Control Plane DNS Endpoint feature - this exposes a public URL to your GKE control place that is protected by GCP. You can read more about it on the GCP docs Link 1 Link 2

Authentication / Authorization

Authorization is carried out through access entries and proper policy association using the following set of GCP IAM permissions:

  • container.clusters.connect

  • container.clusters.get

  • container.clusters.getCredentials

  • container.clusters.list

  • container.cronJobs.list

  • container.daemonSets.list

  • container.deployments.list

  • container.events.get

  • Container.events.list

  • container.jobs.list

  • container.namespaces.list

  • container.nodes.list

  • container.pods.list

  • container.replicaSets.list

  • container.statefulSets.list

Our integration script apply this at the Org level so you won’t have to do it for every cluster.

Cost Data

We fetch billing data using GCP native GKE detailed billing export. Every cluster needs to have the enable-cost-allocation flag turned on.

After this integration, we connect the platform to api-server and metric-server server to gather resource utilization metrics, telemetry and metadata at the cluster level.

Did this answer your question?