← Documentation
GCP

GCP Resource Parking - Supported Capabilities by Service

Exactly what Park Your Cloud (PYC) automatically starts and stops ("parks") on Google Cloud for your project, and what falls outside PYC's current scope. This reflects what PYC's GCP resource discovery and start/stop automation actually support today.

ServicePYC SupportsPYC Does Not Support
Compute Engine (VMs)Start/stop of individual Compute Engine instancesManaged Instance Groups, GKE node pools
Cloud SQLStart/stop of any Cloud SQL instance (MySQL, PostgreSQL, SQL Server)Instances already in SUSPENDED state (billing/legal/KMS issue)
1

Compute Engine (VMs)

Supported
PYC starts and stops individual Compute Engine instances (parking = stop, unparking = start).
Instances in a SUSPENDED state are resumed (not just started) when unparked; when parked from SUSPENDED, PYC stops them through to TERMINATED state.
If an instance is mid-transition (provisioning, staging, stopping, suspending, repairing) when a parking action runs, PYC waits and re-checks automatically before giving up.
Not Supported
Instances that no longer exist, or are in a DEPROVISIONING state, are excluded from discovery and marked as removed rather than acted on.
Managed Instance Groups and GKE node pools are not covered by this VM parking logic - PYC acts on individual instances only.
2

Cloud SQL

Supported
PYC supports start/stop for Cloud SQL instances across all database engines Cloud SQL offers (MySQL, PostgreSQL, and SQL Server).
PYC waits through PENDING_CREATE/MAINTENANCE transitions before reporting failure.
Not Supported
Cloud SQL instances already in a SUSPENDED state (billing, legal, or KMS key issue) are excluded from discovery and cannot be started or stopped by PYC - they require manual intervention outside PYC.
Instances in FAILED or PENDING_DELETE state cannot be started or stopped - no action is taken.
Note

This page currently covers Compute Engine and Cloud SQL - the GCP services PYC's resource discovery and start/stop automation support today. Other GCP services (GKE, Cloud Run, Cloud Functions, etc.) are out of scope until added to the platform.