Skip to content

Commit

Permalink
GCP - more detailed information on image
Browse files Browse the repository at this point in the history
  • Loading branch information
Cyril Diagne committed Oct 12, 2019
1 parent e6b43f2 commit f4f81a7
Showing 1 changed file with 16 additions and 2 deletions.
18 changes: 16 additions & 2 deletions images/providers/gcp/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -2,8 +2,22 @@

Hacky & bare implementation with shell scripts.

/!\ The service account associated with the credentials json must have the "container.clusterRoleBindings.create" permission.

You can add it by running:

```
gcloud projects add-iam-policy-binding <project> \
--member=serviceAccount:<service-account>@developer.gserviceaccount.com \
--role=roles/container.admin
```

# Limitations

- The "Compute Engine API - GPUs (all regions)" quota must be requested manually [here](https://console.cloud.google.com/iam-admin/quotas?metric=GPUs%20(all%20regions))
- The "Compute Engine API - GPUs (all regions)" quota must be requested manually [here](<https://console.cloud.google.com/iam-admin/quotas?metric=GPUs%20(all%20regions)>)
- By default, the system node and the load balancer will be kept on, incuring charges of about 45€ per months. You can manually scale down the system node to 0 to temporarily stop its associated charges or run `kuda delete` to completely delete the cluster.
- Currently the load balancer doesn't get deleted when you delete the cluster. Make sure to delete it manually [here](https://console.cloud.google.com/net-services/loadbalancing/loadBalancers/list) after deleting a cluster to avoid extra costs.
- You can find a list of parameters that you can override in `.config.sh`
- You can find a list of parameters that you can override in `.config.sh`

# Development

0 comments on commit f4f81a7

Please sign in to comment.