here are my suggestions to solve the problems.
- minio: Minio is an application which serves a s3 backend to store the workspace data. When you run Gitpod on GCP, as you do, minio is not needed and can be disabled in the values.yml. To allow Gitpod to store the data directly to the GCP storage a service-account is needed. So you have to create one on GCP with the permission as a Storage Admin . You also need a key in JSON format for that account.
# disabling minio
# configuring access to the storage:
- registry: The same as minio, the registry is a simple docker-registry which is not needed using GCP. You can create a registry for the Gitpod images on GCP instead. After the creation, you need an key for the registry.
# name must not end with a "/"
We encourage you to use both services. Otherwise using the builtin minio and docker-registry will use persistent disks and other compute resources which will be more expensive than the storage and registry backend of GCP.