You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
**Prerequisite:** dind-volume-provisioner should have permissions to create/delete/get of google disks
87
-
There are 3 options:
87
+
##### **GCE Disks**
88
+
*Prerequisite:* volume provisioner (dind-volume-provisioner) should have permissions to create/delete/get of google disks
89
+
There are 3 options to provide cloud credentials on GCE:
88
90
* run venona dind-volume-provisioniner on node with iam role which is allowed to create/delete/get of google disks
89
91
* create Google Service Account with ComputeEngine.StorageAdmin, download its key and pass it to venona installed with `--set-file=Storage.GooogleServiceAccount=/path/to/google-service-account.json`
90
92
* use [Google Workload Identity](https://cloud.google.com/kubernetes-engine/docs/how-to/workload-identity) to assign iam role to `volume-provisioner-venona` service account
91
93
92
-
**Note**: Builds will be running in single availability zone, so you must to specify AvailabilityZone params
94
+
*Note*: Builds will be running in single availability zone, so you must to specify AvailabilityZone params
*Prerequisite:* volume provisioner (dind-volume-provisioner) should have permissions to create/delete/get of aws ebs
108
+
Minimal iam policy for dind-volume-provisioner:
109
+
```json
110
+
{
111
+
"Version": "2012-10-17",
112
+
"Statement": [
113
+
{
114
+
"Effect": "Allow",
115
+
"Action": [
116
+
"ec2:AttachVolume",
117
+
"ec2:CreateSnapshot",
118
+
"ec2:CreateTags",
119
+
"ec2:CreateVolume",
120
+
"ec2:DeleteSnapshot",
121
+
"ec2:DeleteTags",
122
+
"ec2:DeleteVolume",
123
+
"ec2:DescribeInstances",
124
+
"ec2:DescribeSnapshots",
125
+
"ec2:DescribeTags",
126
+
"ec2:DescribeVolumes",
127
+
"ec2:DetachVolume"
128
+
],
129
+
"Resource": "*"
130
+
}
131
+
]
132
+
}
133
+
```
134
+
135
+
There are 3 options to provide cloud credentials on AWS:
136
+
* run venona dind-volume-provisioniner on node with the iam role - use `--kube-node-selector=` option
137
+
* create AWS IAM User, assign it the permissions above and suppy aws credentials to venona installer `--set-value=Storage.AwsAccessKeyId=ABCDF --set-value=Storage.AwsSecretAccessKey=ZYXWV`
138
+
139
+
* use [Aws Identity for Service Account](https://docs.aws.amazon.com/eks/latest/userguide/iam-roles-for-service-accounts.html) to assign iam role to `volume-provisioner-venona` service account
140
+
141
+
*Notes*:
142
+
- Builds will be running in single availability zone, so you must specify AvailabilityZone parameter `--set-value=Storage.AvailabilityZone=<aws-az>` and build-node-selector `--build-node-selector=failure-domain.beta.kubernetes.io/zone=<aws-az>` in case of multizone cluster
143
+
144
+
- We support both [in-tree ebs](https://kubernetes.io/docs/concepts/storage/volumes/#awselasticblockstore) (`--set-value=Storage.Backend=ebs`) volumes and ebs-csi(https://github.com/kubernetes-sigs/aws-ebs-csi-driver) (`--set-value=Storage.Backend=ebs-csi`)
0 commit comments