GKE Node Auto-Upgrade Not Configured
Nodes stay on old versions, so published Kubernetes vulnerabilities remain unpatched until someone upgrades them by hand.
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 node auto-upgrade 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
- Open the GKE cluster in the GCP Console and navigate to Node Pools.
- For each node pool, enable Auto-upgrade under the Management section.
- Enable Auto-repair as well to automatically replace unhealthy nodes.
- Set a maintenance window to control when upgrades are applied.
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-120- 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.