Compute & Runtime 1 documented workflow

GKE

Pro cluster workflows with opt-in k3d runtime integration.

Documented workflows

1 workflows
  • clusters CRUD

Service boundaries

  • Kubernetes runtime parity depends on host runtime/k3d integration.
  • [prod_only] Node pools, autoscaling, and upgrades (GCP-managed cluster autoscaler, regional instance groups).
  • clusters CRUD: Local facade exists for cluster metadata and k3d-oriented workflows.
  • node pools, autoscaling, upgrades: Not supported locally. Production cluster management; local k3d provides the runtime cluster.
  • Audited metadata survives restart while the LocalCloud volume is retained
  • External runtime/data-plane side effects, if any, have separate lifecycle and recovery limits.

Next steps