Skip to content

feat(qov-1844) Add step to configure correctly service account cluster #166

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
mzottola merged 1 commit into from
Jun 30, 2026
+26 −2
Merged

feat(qov-1844) Add step to configure correctly service account cluster #166

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
28 changes: 26 additions & 2 deletions docs/configuration/integrations/kubernetes/gke/managed.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -88,7 +88,6 @@ gcloud kms keys add-iam-policy-binding <KEY_NAME> \
--member="serviceAccount:service-<CLUSTER_PROJECT_NUMBER>@compute-system.iam.gserviceaccount.com" \
--role="roles/cloudkms.cryptoKeyEncrypterDecrypter"
```

<Info>
`<KMS_KEY_PROJECT_ID>` - the GCP project ID of the project where your KMS key is stored (e.g. my-test-project)

Expand All @@ -103,7 +102,32 @@ gcloud kms keys add-iam-policy-binding <KEY_NAME> \
`<KEY_NAME>` - the name of the KMS key (e.g. my-key)
</Info>

#### Step 3 - Set your KMS key on cluster creation
#### Step 3 - Grant your cluster service account on your KMS key

<Warning>
This step is needed only for GKE clusters in a different project than the KMS key created
</Warning>

* Create dedicated role in your KMS Key project:
```bash
gcloud iam roles create qovery-role-kms-get-iam-policy \
--project=<KMS_KEY_PROJECT_ID> \
--title="Qovery KMS Get IAM Policy" \
--description="Allows reading IAM policy on KMS resources only" \
--permissions=cloudkms.cryptoKeys.getIamPolicy \
--stage=GA
```
* Grant your service account on your kms key with the new role:
```bash
gcloud kms keys add-iam-policy-binding <KEY_NAME> \
--keyring=<KEY_RING> \
--location=<LOCATION> \
--project=<KMS_KEY_PROJECT_ID> \
--member="serviceAccount:<SERVICE_ACCOUNT_EMAIL>" \
--role="projects/<KMS_KEY_PROJECT_ID>/roles/qovery-role-kms-get-iam-policy"
```

#### Step 4 - Set your KMS key on cluster creation

Enable the GKE KMS key option when creating your cluster:
<Frame>
Expand Down
Loading