GCP Dependencies
GCP-specific requirements only. Everything cloud-agnostic (PostgreSQL extensions, artifact access, domain names, secrets handling) is defined once in the Environment Dependencies registry; this page refines those rows for GKE.
Validation status
GCP is field-validated for guard-only deployments on GKE with customer-provided (bring-your-own) prerequisites. A full-platform GCP requirements set is still being consolidated; confirm specifics with your DynamoAI deployment engineer before committing to a topology.
Cluster
| Dependency | Requirement | Why It Is Needed | Verify |
|---|---|---|---|
| GKE cluster | A provisioned GKE cluster with the default CSI driver providing a default StorageClass, and cluster autoscaling for CPU and GPU capacity. | Backs pod networking, service discovery, and volume provisioning for the platform. | kubectl get nodes returns Ready nodes; a test PersistentVolume provisions via the default StorageClass. |
| Workload Identity | GKE Workload Identity configured for workloads that access Google Cloud resources. | Pods use federated identities instead of exported service-account keys. | A test pod acquires a token for its target resource. |
Compute
| Dependency | Requirement | Why It Is Needed | Verify |
|---|---|---|---|
| GPU nodes | GPU node pools with NVIDIA GPUs whose driver satisfies the core CUDA requirement (currently CUDA 13.0). Confirm the machine family and regional quota with your DynamoAI deployment engineer. | DynamoGuard inference and training run on these nodes. | GPU nodes provision and advertise nvidia.com/gpu capacity. |
| CPU nodes | General-purpose or compute-optimized CPU capacity through cluster autoscaling. | DynamoGuard base functions and DynamoEval run on these nodes. | Autoscaling provisions CPU nodes on demand. |
Databases and Storage
| Dependency | Requirement | Why It Is Needed | Verify |
|---|---|---|---|
| PostgreSQL | A managed PostgreSQL instance (for example Cloud SQL) satisfying the core PostgreSQL row, including the pg_partman and vector extensions and the dfl and keycloak databases. | Primary relational store; extension availability must be confirmed for the chosen service tier. | Extensions install successfully; endpoint reachable from the cluster over private connectivity. |
| Object storage | S3-compatible storage with two logical stores (models, platform artifacts): bring-your-own or DynamoAI-deployed in-cluster. | Concrete GCP form of the core object-storage requirement. | Endpoint, store names, and credentials configured and reachable from the cluster. |
Networking and Ingress
| Dependency | Requirement | Why It Is Needed | Verify |
|---|---|---|---|
| Ingress | An ingress path for the three platform endpoints (apps., auth., api.) with certificates. The GCE ingress class is field-validated. | Exposes the platform to the customer network; the final handover check depends on it. | All three endpoints respond over HTTPS from the customer network. |
Known Issues
No GCP-specific known issues are currently recorded.
Pre-Deployment Checklist
Your progress is saved in your browser. Use Download to export the current state as Markdown.
GCP Pre-Deployment0/10