To deploy Dagster to GCP, Google Compute Engine (GCE) can host Dagit, Google Cloud SQL can store runs and events, and Google Cloud Storage (GCS) can act as an IO manager.
We recommend launching a Cloud SQL PostgreSQL instance for run and events data. You can configure Dagit to use Cloud SQL to run and events data by setting blocks in your $DAGSTER_HOME/dagster.yaml appropriately:
In this case, you'll want to ensure you provide the right connection strings for your Cloud SQL instance, and that the node or container hosting Dagit is able to connect to Cloud SQL.
Be sure that this file is present, and DAGSTER_HOME is set, on the node where Dagit is running.
Note that using Cloud SQL for run and event log storage does not require that Dagit be running in the cloud. If you are connecting a local Dagit instance to a remote Cloud SQL storage, double check that your local node is able to connect to Cloud SQL.
You'll probably also want to configure a GCS bucket to store op outputs via persistent IO Managers. This enables reexecution, review and audit of op outputs, and cross-node cooperation (e.g., with the multiprocess_executor or celery_executor).