Why this matters: when your cluster runs on a managed cloud Kubernetes service (EKS, AKS, or GKE), the cloud provider runs the control plane — so onboarding is about connecting Mavvrik to that service's own API/telemetry, not deploying infrastructure from scratch. Each provider has its own connection methods (allocation-based, appliance-based, or managed-Prometheus), covered separately below.
Before you start: you'll need admin/owner access to the specific cloud provider's console for the cluster you're onboarding.