Skip to content

Commit 3743c60

Browse files
Andrew Farriesroboquat
authored andcommitted
Add new section to GCP troubleshooting doc
Explain the permissions required to install helm charts to the new cluster.
1 parent 3ce4a47 commit 3743c60

File tree

1 file changed

+14
-0
lines changed

1 file changed

+14
-0
lines changed

install/infra/single-cluster/gcp/README.md

Lines changed: 14 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -223,6 +223,20 @@ gcloud auth activate-service-account --key-file=/path/to/account/key.json
223223
gcloud container clusters get-credentials <cluster_name> --region <region> --zone <zone> --project <project>
224224
```
225225

226+
### Failed to install helm charts to the cluster
227+
228+
If you see errors like:
229+
230+
```
231+
Error: clusterroles.rbac.authorization.k8s.io is forbidden: User "xxxxx@developer.gserviceaccount.com" cannot create resource "clusterroles" in API group "rbac.authorization.k8s.io" at the cluster scope: requires one of ["container.clusterRoles.create"] permission(s).
232+
233+
│ with module.certmanager.helm_release.cert,
234+
│ on ../../modules/tools/cert-manager/main.tf line 17, in resource "helm_release" "cert":
235+
│ 17: resource "helm_release" "cert" {
236+
237+
```
238+
After running `make apply`, ensure that the service account you are using has the `Kubernetes Engine Admin` role. See the [GCP IAM documentation](https://cloud.google.com/iam/docs/granting-changing-revoking-access) to learn how to associate roles with a service account.
239+
226240
## Cleanup
227241

228242
Make sure you first delete the `gitpod` resources in the cluster so things like load balancer created by the k8s `service` gets deleted. Otherwise terraform will not be able to delete the VPC.

0 commit comments

Comments
 (0)