Google Compute Engine persistent disk Container Storage Interface (CSI) Driver

The Compute Engine persistent disk Container Storage Interface (CSI) Driver is a CSI compliant driver that you can use to manage the lifecycle of your Google Compute Engine persistent disks.

Before you can deploy storage templates to clusters in your location, make sure you set up Satellite Config by selecting the Enable cluster admin access for Satellite Config option in the console or including the --enable-config-admin option when you create your cluster.

You cannot scope Satellite storage service to resource groups. However, if you are scoping other resources such as location and cluster to resource groups, you need to add Satellite reader and link administrator role for all resources in the account.

Prerequisites

Creating and assigning a configuration in the console

Review the parameter reference.
From the Locations console, select the location where you want to create a storage configuration.
Select Storage > Create storage configuration
Enter a name for your configuration.
Select the Storage type.
Select the Version and click Next
If the Storage type that you selected accepts custom parameters, enter them on the Parameters tab.
If the Storage type that you selected requires secrets, enter them on the Secrets tab.
On the Storage classes tab, review the storage classes that are deployed by the configuration or create a custom storage class.
On the Assign to service tab, select the service that you want to assign your configuration to.
Click Complete to assign your storage configuration.

Creating a configuration in the CLI

Review the parameter reference for the template version that you want to use.
Log in to the IBM Cloud CLI.
```
ibmcloud login
```
List your Satellite locations and note the Managed from column.
```
ibmcloud sat location ls
```
Target the Managed from region of your Satellite location. For example, for wdc target us-east. For more information, see Satellite regions.
```
ibmcloud target -r us-east
```
If you use a resource group other than default, target it.
```
ibmcloud target -g <resource-group>
```

Copy one of the following example command for the template version that you want to use. For more information about the command, see ibmcloud sat storage config create in the command reference.

Example command to create a version 1.0.4 configuration.

ibmcloud sat storage config create --location LOCATION --name NAME --template-name gcp-compute-persistent-disk-csi-driver --template-version 1.0.4 --param "project_id=PROJECT_ID"  --param "private_key_id=PRIVATE_KEY_ID"  --param "private_key=PRIVATE_KEY"  --param "client_email=CLIENT_EMAIL"  --param "client_id=CLIENT_ID"  --param "auth_uri=AUTH_URI"  --param "token_uri=TOKEN_URI"  --param "auth_provider_x509_cert_url=AUTH_PROVIDER_X509_CERT_URL"  --param "client_x509_cert_url=CLIENT_X509_CERT_URL"

Example command to create a version 1.7.1 configuration.

ibmcloud sat storage config create --location LOCATION --name NAME --template-name gcp-compute-persistent-disk-csi-driver --template-version 1.7.1 --param "project_id=PROJECT_ID"  --param "private_key_id=PRIVATE_KEY_ID"  --param "private_key=PRIVATE_KEY"  --param "client_email=CLIENT_EMAIL"  --param "client_id=CLIENT_ID"  --param "auth_uri=AUTH_URI"  --param "token_uri=TOKEN_URI"  --param "auth_provider_x509_cert_url=AUTH_PROVIDER_X509_CERT_URL"  --param "client_x509_cert_url=CLIENT_X509_CERT_URL"

Example command to create a version 1.8.0 configuration.

ibmcloud sat storage config create --location LOCATION --name NAME --template-name gcp-compute-persistent-disk-csi-driver --template-version 1.8.0 --param "project_id=PROJECT_ID"  --param "private_key_id=PRIVATE_KEY_ID"  --param "private_key=PRIVATE_KEY"  --param "client_email=CLIENT_EMAIL"  --param "client_id=CLIENT_ID"  --param "auth_uri=AUTH_URI"  --param "token_uri=TOKEN_URI"  --param "auth_provider_x509_cert_url=AUTH_PROVIDER_X509_CERT_URL"  --param "client_x509_cert_url=CLIENT_X509_CERT_URL"

Customize the command based on the settings that you want to use.
Run the command to create a configuration.

Verify your configuration was created.

ibmcloud sat storage config get --config CONFIG

Creating a configuration in the API

Generate an API key, then request a refresh token. For more information, see Generating an IBM Cloud IAM token by using an API key.
Review the parameter reference for the template version that you want to use.

Copy one of the following example requests and replace the variables that you want to use.

Example request to create a version 1.0.4 configuration.

curl -X POST "https://containers.cloud.ibm.com/global/v2/storage/satellite/createStorageConfigurationByController" -H "accept: application/json" -H "Authorization: TOKEN" -H "Content-Type: application/json" -d "{ \"config-name\": \"string\", \"controller\": \"string\", \"storage-class-parameters\": [ { \"additionalProp1\": \"string\", \"additionalProp2\": \"string\", \"additionalProp3\": \"string\" } ], \"storage-template-name\": \"gcp-compute-persistent-disk-csi-driver\", \"storage-template-version\": \"1.0.4\", \"update-assignments\": true, \"user-config-parameters\":\"user-secret-parameters\": { \"entry.name\": \"PROJECT_ID\",{ \"entry.name\": \"PRIVATE_KEY_ID\",{ \"entry.name\": \"PRIVATE_KEY\",{ \"entry.name\": \"CLIENT_EMAIL\",{ \"entry.name\": \"CLIENT_ID\",{ \"entry.name\": \"AUTH_URI\",{ \"entry.name\": \"TOKEN_URI\",{ \"entry.name\": \"AUTH_PROVIDER_X509_CERT_URL\",{ \"entry.name\": \"CLIENT_X509_CERT_URL\",}

Example request to create a version 1.7.1 configuration.

curl -X POST "https://containers.cloud.ibm.com/global/v2/storage/satellite/createStorageConfigurationByController" -H "accept: application/json" -H "Authorization: TOKEN" -H "Content-Type: application/json" -d "{ \"config-name\": \"string\", \"controller\": \"string\", \"storage-class-parameters\": [ { \"additionalProp1\": \"string\", \"additionalProp2\": \"string\", \"additionalProp3\": \"string\" } ], \"storage-template-name\": \"gcp-compute-persistent-disk-csi-driver\", \"storage-template-version\": \"1.7.1\", \"update-assignments\": true, \"user-config-parameters\":\"user-secret-parameters\": { \"entry.name\": \"PROJECT_ID\",{ \"entry.name\": \"PRIVATE_KEY_ID\",{ \"entry.name\": \"PRIVATE_KEY\",{ \"entry.name\": \"CLIENT_EMAIL\",{ \"entry.name\": \"CLIENT_ID\",{ \"entry.name\": \"AUTH_URI\",{ \"entry.name\": \"TOKEN_URI\",{ \"entry.name\": \"AUTH_PROVIDER_X509_CERT_URL\",{ \"entry.name\": \"CLIENT_X509_CERT_URL\",}

Example request to create a version 1.8.0 configuration.

curl -X POST "https://containers.cloud.ibm.com/global/v2/storage/satellite/createStorageConfigurationByController" -H "accept: application/json" -H "Authorization: TOKEN" -H "Content-Type: application/json" -d "{ \"config-name\": \"string\", \"controller\": \"string\", \"storage-class-parameters\": [ { \"additionalProp1\": \"string\", \"additionalProp2\": \"string\", \"additionalProp3\": \"string\" } ], \"storage-template-name\": \"gcp-compute-persistent-disk-csi-driver\", \"storage-template-version\": \"1.8.0\", \"update-assignments\": true, \"user-config-parameters\":\"user-secret-parameters\": { \"entry.name\": \"PROJECT_ID\",{ \"entry.name\": \"PRIVATE_KEY_ID\",{ \"entry.name\": \"PRIVATE_KEY\",{ \"entry.name\": \"CLIENT_EMAIL\",{ \"entry.name\": \"CLIENT_ID\",{ \"entry.name\": \"AUTH_URI\",{ \"entry.name\": \"TOKEN_URI\",{ \"entry.name\": \"AUTH_PROVIDER_X509_CERT_URL\",{ \"entry.name\": \"CLIENT_X509_CERT_URL\",}

Creating an assignment in the CLI

List your storage configurations and make a note of the storage configuration that you want to assign to your clusters.
```
ibmcloud sat storage config ls
```
Get the ID of the cluster, cluster group, or service that you want to assign storage to.

To make sure that your cluster is registered with Satellite Config or to create groups, see Setting up clusters to use with Satellite Config.

Example command to list cluster groups.
```
ibmcloud sat group ls
```
Example command to list clusters.
```
ibmcloud oc cluster ls --provider satellite
```
Example command to list Satellite services.
```
ibmcloud sat service ls --location <location>
```
Assign your storage configuration to the cluster, group, or service that you retrieved earlier. For more information, see the ibmcloud sat storage assignment create command.

Example command to assign a configuration to a cluster group.
```
ibmcloud sat storage assignment create --group GROUP --config CONFIG --name NAME
```
Example command to assign a configuration to a cluster.
```
ibmcloud sat storage assignment create --cluster CLUSTER --config CONFIG --name NAME
```
Example command to assign a configuration to a service cluster.
```
ibmcloud sat storage assignment create --service-cluster-id CLUSTER --config CONFIG --name NAME
```

Verify that your assignment is created.

ibmcloud sat storage assignment ls (--cluster CLUSTER | --config CONFIG | --location LOCATION | --service-cluster-id CLUSTER)

Creating a storage assignment in the API

Copy one of the following example requests.

Example request to assign a configuration to a cluster.

curl -X POST "https://containers.cloud.ibm.com/global/v2/storage/satellite/createAssignmentByCluster" -H "accept: application/json" -H "Authorization: Bearer TOKEN" -H "Content-Type: application/json" -d "{ \"channelName\": \"CONFIGURATION-NAME\", \"cluster\": \"CLUSTER-ID\", \"controller\": \"LOCATION-ID\", \"name\": \"ASSIGNMENT-NAME\"}"

Example request to assign configuration to a cluster group.

curl -X POST "https://containers.cloud.ibm.com/global/v2/storage/satellite/createAssignment" -H "accept: application/json" -H "Authorization: Bearer TOKEN" -H "Content-Type: application/json" -d "{ \"channelName\": \"CONFIGURATION-NAME\", \"cluster\": \"string\", \"groups\": [ \"CLUSTER-GROUP\" ], \"name\": \"ASSIGNMENT-NAME\"}"

Replace the variables with your details and run the request.

Verify the assignment was created by listing your assignments.

curl -X GET "https://containers.cloud.ibm.com/global/v2/storage/satellite/getAssignments" -H "accept: application/json" -H "Authorization: Bearer TOKEN"

Updating storage assignments in the console

You can use the Satellite console to apply the latest patch updates to your assignments.

From the Locations page in the Satellite console, select your location.
Click the Storage tab to view your configurations.
Click the configuration you want to update.
Click information Information (i) icon to apply the latest revision or patch.
Optional: Enable automatic patch updates for your storage assignment. Enabling automatic patch updates ensures that your assignment always has the latest security fixes.

If you enable automatic patch updates, you must still apply major updates manually.

Manually upgrading assignments in the CLI

Upgrade an assignment to use the latest storage template revision.

List your Satellite storage assignments, make a note of the Satellite assignment you want to upgrade.
```
ibmcloud sat storage assignment ls
```
List the Satellite storage templates to see the latest available versions.
```
ibmcloud sat storage template ls
```
Upgrade the Satellite assignment.

Example command to upgrade an assignment.
```
ibmcloud sat storage assignment upgrade --assignment ASSIGNMENT
```

Enabling automatic patch updates for configurations and assignments in the CLI

You can use the sat storage assignment autopatch enable CLI to enable automatic patch updates for your assignments. Enabling automatic patch updates applies the latest storage template revisions (patches) automatically. You must still apply major updates manually.

List your Satellite storage configurations. Make a note of the configuration ID.
```
ibmcloud sat storage assignment ls
```
Run one of the following example commands to enable automatic patch updates for your configuration and its associated assignments. Enter the configuration ID that you retrieved in the previous step.

Example command to enable automatic patch updates for an assignment.
```
ibmcloud sat storage assignment autopatch enable --config CONFIG  (--all | --assignment ASSIGNMENT-ID [--assignment ASSIGNMENT-ID])
```
Example command to enable automatic patch updates for all storage assignments under a given configuration.
```
ibmcloud sat storage assignment autopatch enable --config CONFIG --all
```
Example command to disable automatic patch updates for all assignments under a specific configuration.
```
ibmcloud sat storage assignment autopatch disable --config CONFIG --all
```
Example command to disable automatic patch updates for an single assignment and a specific configuration.
```
ibmcloud sat storage assignment autopatch disable --config CONFIG --assignment ASSIGNMENT-ID
```
Example command to disable automatic patch updates for an multiple assignment and a specific configuration.
```
ibmcloud sat storage assignment autopatch disable --config CONFIG --assignment ASSIGNMENT-ID --assignment ASSIGNMENT-ID
```

Upgrading a configuration and assignments in the API

You can use the /v2/storage/satellite/updateAssignment API to update your assignments with new clusters or cluster groups. Set updateConfigVersion to true to apply the revision update.

Copy the following example request and replace the variables for the cluster groups and assignments that you want to update.

curl -X PATCH "https://containers.cloud.ibm.com/global/v2/storage/satellite/updateAssignment" -H "accept: application/json" -H "Authorization: Bearer TOKEN" -H "Content-Type: application/json" -d "{ \"groups\": [ \"CLUSTER-GROUPS\" ], \"name\": \"ASSIGNMENT-NAME\", \"updateConfigVersion\": true, \"uuid\": \"ASSIGNMENT-ID\"}"

Run the request.

Get the details of you assignment to verify the update.

curl -X GET "https://containers.cloud.ibm.com/global/v2/storage/satellite/getAssignment?uuid=ASSIGNMENT-ID" -H "accept: application/json" -H "Authorization: Bearer TOKEN"

Enabling automatic patch updates for assignments in the API

You can use the /v2/storage/satellite/setAssignmentAutoupgrade API to enable automatic patch updates for your assignments. Enabling automatic patch updates applies the latest storage template revisions (patches) automatically. You must still apply major updates manually.

Copy the following example request and replace the variables for the cluster groups and assignments that you want to update.

curl -X PATCH "https://containers.cloud.ibm.com/global/v2/storage/satellite/setAssignmentAutoupgrade" -H "accept: application/json" -H "Authorization: Bearer TOKEN" -H "Content-Type: application/json" -d { "config": "string", "controller": "string", "autopatch": boolean,"assignment" : { "all": boolean, "uuid": ["string", "string", ...], } }

Run the request.

Get the details of you assignment to verify the upgrade.

curl -X GET "https://containers.cloud.ibm.com/global/v2/storage/satellite/getAssignment?uuid=ASSIGNMENT-ID" -H "accept: application/json" -H "Authorization: Bearer TOKEN"

Deploying an app that uses Google Compute Engine persistent disk

You can use the gce-pd-csi-driver to create PVCs that you can use in your cluster workloads.

Create a PVC that references a GCP storage class that you created earlier.

apiVersion: v1
kind: PersistentVolumeClaim
metadata:
  name: pvc-gce
spec:
  accessModes:
    - ReadWriteOnce
  resources:
    requests:
      storage: 10Gi
  storageClassName: sat-gce-block-silver

Create the PVC in your cluster.
```
oc apply -f pvc-gce.yaml
```

Create a YAML configuration file for a pod that mounts the PVC that you created.

apiVersion: apps/v1
kind: StatefulSet
metadata:
  name: statefulset-gce
  labels:
    app: nginx
spec:
  podManagementPolicy: Parallel  # default is OrderedReady
  serviceName: statefulset-gce
  replicas: 1
  template:
    metadata:
      labels:
        app: nginx
    spec:
      nodeSelector:
        "kubernetes.io/os": linux
      containers:
        - name: statefulset-gce
          image: mcr.microsoft.com/oss/nginx/nginx:1.19.5
          command:
            - "/bin/bash"
            - "-c"
            - set -euo pipefail; while true; do echo $(date) >> /mnt/gce/outfile; sleep 1; done
          volumeMounts:
            - name: persistent-storage
              mountPath: /mnt/gce
  updateStrategy:
    type: RollingUpdate
  selector:
    matchLabels:
      app: nginx
  volumeClaimTemplates:
    - metadata:
        name: persistent-storage
        annotations:
          volume.beta.kubernetes.io/storage-class: sat-gce-block-silver
      spec:
        accessModes: ["ReadWriteOnce"]
        resources:
          requests:
            storage: 10Gi

Create the pod in your cluster.
```
oc apply -f statefulset-gce.yaml
```

Verify that the pod is deployed. Note that it might take a few minutes for your app to get into a Running state.

oc get pods

NAME                                READY   STATUS    RESTARTS   AGE
statefulset-gce                          1/1     Running   0          2m58s

Verify that the app can write to your persistent disk by logging in to your pod.
```
oc exec web-server -it bash
```
View the contents of the outfile file to confirm that your app can write data to your persistent storage.
```
cat /mnt/gce/outfile
```
Example output
```
Fri Jul 16 07:49:39 EDT 2021
Fri Jul 16 07:49:39 EDT 2021
Fri Jul 16 07:49:39 EDT 2021
```
Exit the pod.
```
exit
```

Removing Compute Engine storage from your apps

If you no longer need your Google Compute Engine configuration, you can remove your apps, PVCs, PVs, and assignment from your clusters.

List your PVCs and note the name of the PVC that you want to remove.
```
oc get pvc
```

Remove any pods that mount the PVC. List all the pods that currently mount the PVC that you want to delete. If no pods are returned, you do not have any pods that currently use your PVC.

oc get pods --all-namespaces -o=jsonpath='{range .items[*]}{"\n"}{.metadata.name}{":\t"}{range .spec.volumes[*]}{.persistentVolumeClaim.claimName}{" "}{end}{end}' | grep "<pvc_name>"

Example output

app    sat-gce-block-platinum

Remove the pod that uses the PVC. If the pod is part of a deployment or statefulset, remove the deployment or statefulset.
```
oc delete pod <pod_name>
```
```
oc delete deployment <deployment_name>
```
```
oc delete statefulset <statefulset_name>
```
Verify that the pod, deployment, or statefulset is removed.
```
oc get pods
```
```
oc get deployments
```
```
oc get statefulset
```
Delete the PVC.
```
oc delete pvc <pvc_name>
```
Verify that your PV is automatically removed.
```
oc get pv
```

Removing the Compute Engine storage configuration from your cluster

If you no longer plan on using your persistent disk storage in your cluster, you can use the CLI unassign your cluster from the storage configuration.

Note that if you remove the storage configuration, the driver is then uninstalled from all assigned clusters. Your PVCs, PVs, and data are not removed. However, you might not be able to access your data until you re-install the driver in your cluster again.

Removing the Google Compute Engine storage configuration from the console

Use the console to remove a storage configuration.

From the Satellite storage dashboard, select the storage configuration you want to delete.
Select Actions > Delete
Enter the name of your storage configuration.
Select Delete.

Removing the Google Compute Engine storage configuration from the CLI

List your storage assignments and find the one that you used for your cluster.

ibmcloud sat storage assignment ls (--cluster CLUSTER | --config CONFIG | --location LOCATION | --service-cluster-id CLUSTER)

Remove the assignment. After the assignment is removed, the driver pods and storage classes are removed from all clusters that were part of the storage assignment.
```
ibmcloud sat storage assignment rm --assignment <assignment_ID>
```
Verify that the driver is removed from your cluster.
1. List of the storage classes in your cluster and verify that the storage classes are removed.
```
oc get sc
```
2. List the pods in the kube-system namespace and verify that the storage driver pods are removed.
```
oc get pods -n kube-system | grep gce
```
Optional: Remove the storage configuration.
1. List the storage configurations.
```
ibmcloud sat storage config ls
```
2. Remove the storage configuration.
```
ibmcloud sat storage config rm --config <config_name>
```

Parameter reference

1.0.4 parameter reference

1.0.4 parameter reference
Display name	CLI option	Type	Description	Required?	Default value
Google Cloud project ID.	`project_id`	Secret	Google Cloud project ID. You can find your Project ID from the Google Cloud dashboard.	true	N/A
Google Cloud private key ID	`private_key_id`	Secret	Google Cloud private key ID. You can find this in the JSON service account key file.	true	N/A
Private key of the service account.	`private_key`	Secret	Private key of the service account. You can find the service account key on the Service Account section of the project dashboard.	true	N/A
Client email	`client_email`	Secret	The email of the service account can be found in the IAM & Admin section of the project dashboard.	true	N/A
Client ID	`client_id`	Secret	Client ID. You can find the Client ID in the APIs & Services section of the project dashboard.	true	N/A
Authorization URI	`auth_uri`	Secret	Authorization URI for the service account. You can find this in the JSON service account key file.	true	N/A
Token URI	`token_uri`	Secret	Token URI for the service account. You can find this in the JSON service account key file.	true	N/A
URL for the authorization provider certificate	`auth_provider_x509_cert_url`	Secret	URL for the authorization provider certificate. You can find this in the JSON service account key file.	true	N/A
URL for the client certificate	`client_x509_cert_url`	Secret	URL for the client certificate. You can find this in the JSON service account key file.	true	N/A

1.7.1 parameter reference

1.7.1 parameter reference
Display name	CLI option	Type	Description	Required?	Default value
Google Cloud project ID	`project_id`	Secret	Google Cloud project ID. You can find your Project ID from the Google Cloud dashboard.	true	N/A
Google Cloud private key ID	`private_key_id`	Secret	Google Cloud private key ID. You can find this in the JSON service account key file.	true	N/A
Private key of the service account	`private_key`	Secret	Private key of the service account. You can find the service account key on the Service Account section of the project dashboard.	true	N/A
Client email	`client_email`	Secret	The email of the service account can be found in the IAM & Admin section of the project dashboard.	true	N/A
Client ID	`client_id`	Secret	Client ID. You can find the Client ID in the APIs & Services section of the project dashboard.	true	N/A
Authorization URI	`auth_uri`	Secret	Authorization URI for the service account. You can find this in the JSON service account key file.	true	N/A
Token URI	`token_uri`	Secret	Token URI for the service account. You can find this in the JSON service account key file.	true	N/A
URL for the authorization provider certificate	`auth_provider_x509_cert_url`	Secret	URL for the authorization provider certificate. You can find this in the JSON service account key file.	true	N/A
URL for the client certificate	`client_x509_cert_url`	Secret	URL for the client certificate. You can find this in the JSON service account key file.	true	N/A

1.8.0 parameter reference

1.8.0 parameter reference
Display name	CLI option	Type	Description	Required?	Default value
Google Cloud project ID	`project_id`	Secret	Google Cloud project ID. You can find your Project ID from the Google Cloud dashboard.	true	N/A
Google Cloud private key ID	`private_key_id`	Secret	Google Cloud private key ID. You can find this in the JSON service account key file.	true	N/A
Private key of the service account	`private_key`	Secret	PrPrivate key of the service account. You can find the service account key on the Service Account section of the project dashboard.	true	N/A
Client email	`client_email`	Secret	The email of the service account can be found in the IAM & Admin section of the project dashboard.	true	N/A
Client ID	`client_id`	Secret	Client ID. You can find the Client ID in the APIs & Services section of the project dashboard.	true	N/A
Authorization URI	`auth_uri`	Secret	Authorization URI for the service account. You can find this in the JSON service account key file.	true	N/A
Token URI	`token_uri`	Secret	Token URI for the service account. You can find this in the JSON service account key file.	true	N/A
URL for the authorization provider certificate	`auth_provider_x509_cert_url`	Secret	URL for the authorization provider certificate. You can find this in the JSON service account key file.	true	N/A
URL for the client certificate	`client_x509_cert_url`	Secret	URL for the client certificate. You can find this in the JSON service account key file.	true	N/A

Storage class reference for Compute Engine

Review the Satellite storage classes for Google compute engine persistent disk storage. You can describe storage classes in the command line with the oc describe sc <storage-class-name> command.

Storage class reference for Google compute engine persistent disk storage
Storage class name	Default Read IOPS per GB	Default Write IOPS per GB	Size range (per disk)	Hard disk	Reclaim policy	Volume Binding Mode
`sat-gce-block-platinum`	NA	NA	500 GB - 64 TB	SSD	Delete	Immediate
`sat-gce-block-platinum-metro`	NA	NA	500 GB - 64 TB	SSD	Delete	WaitForFirstConsumer
`sat-gce-block-gold`	30	30	10 GB - 64 TB	SSD	Delete	Immediate
`sat-gce-block-gold-metro` Default	30	30	10 GB - 64 TB	SSD	Delete	WaitForFirstConsumer
`sat-gce-block-silver`	6	30	10 GB - 64 GB	SSD	Delete	Immediate
`sat-gce-block-silver-metro`	6	6	10 GB - 64 GB	SSD	Delete	WaitForFirstConsumer
`sat-gce-block-bronze`	0.75	1.5	10 GiB - 64 TiB	HDD	Delete	Immediate
`sat-gce-block-bronze-metro`	0.75	1.5	10 GiB - 64 TiB	HDD	Delete	WaitForFirstConsumer

Getting help and support for Google Compute Engine

When you use Google Compute Engine, try the following resources before you open a support case.

Review the FAQs in the Google Cloud docs.
Review the troubleshooting documentation to troubleshoot and resolve common issues.
Check the status of the IBM Cloud platform and resources by going to the Status page.
Review Stack Overflow to see whether other users experienced the same problem. Tag any questions with ibm-cloud and Google-Cloud.
Open an issue in the Google Cloud Console.