Kubernetes | Mavvrik

Why this matters: Kubernetes cost tracking splits along two fundamentally different paths — a managed cloud service (EKS, AKS, GKE) where the provider runs the control plane, versus a self-managed on-prem or self-hosted cluster where you run everything. The onboarding mechanics, and what Mavvrik can see, differ meaningfully between the two.

This shows up differently depending on your role:

Platform/DevOps teams do the actual onboarding — running the Helm install, configuring the appliance or managed-Prometheus integration for whichever path applies to their cluster.
FinOps managers use the resulting data to track Kubernetes spend across every cluster, cloud or on-prem, in one place.

Kubernetes is covered in two paths below, depending on where your cluster runs:

Kubernetes on-prem
Kubernetes on-cloud
Kubernetes Cloud Hosted
Kubernetes Onboarding Questionnaire
Kubernetes Secret Ref Usage
K8s Cluster APIs for IaC Automation
K8s Prometheus on Windows (AKS)