GKE Cluster Monitoring Disabled
There are no cluster metrics, so a degradation is only visible once users report it.
Free to start. No card. The playground just needs your work email.
Google CloudKubernetes
Found, explained, handed over.
Where the estate departs from your policies, frameworks and tagging rules.
Detect
ZopNight checks this automatically across Google Cloud, with read-only access to the account.
Explain
Every finding says exactly what to change: Enable monitoring on the GKE cluster.
Fix
The finding opens with the fix already written out, step by step, so it is one ticket, not an investigation.
- Applies to
- GKE Clusters on Google Cloud
- The fix, by hand
- Confirm the desired metrics-collection scope (SYSTEM is the minimum; many teams add WORKLOADS or APISERVER).
- Update the cluster: gcloud container clusters update ‹name› --location=‹loc› --monitoring=SYSTEM,WORKLOAD.
- Or Cloud Console → Kubernetes Engine → Clusters → the resource → Edit → Features → Cloud Monitoring → set components.
- Verify in Cloud Monitoring → Metrics Explorer → kubernetes.io/container/cpu/limit_utilization appears within 5 minutes.
- If using managed Prometheus, also enable --enable-managed-prometheus on the cluster.
These are the steps the finding carries in the product.
- Category
- Compliance. Configuration drift from best practice: public access, missing MFA, unencrypted storage, deprecated runtimes.
- Where it appears
- The Compliance tab of Recommendations, with every affected resource listed.
- Rule ID
RC-1220- Full reference
Related checks
See the compliance findings in your account.
Connect a read-only role and the first pass runs on your own estate. This check, and the rest of the catalogue, with it.
Prefer to talk it through first? Book 20 minutes with the team.
- $30M+annualised cloud spend under management
- 550K+resources tracked since launch
- 20-60%off the bill in the first month
- SOC 2Type II report, plus ISO 27001
Figures published on zop.dev.