Movatterモバイル変換

[0]ホーム
URL:

Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

 Sign up
Appearance settings

Commitc99d972

Browse files
updated runner installation on GKE
1 parentf35a743 commitc99d972

File tree

1 file changed

+61
-4
lines changed

1 file changed

+61
-4
lines changed

‎_docs/administration/codefresh-runner.md‎

Lines changed: 61 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1309,17 +1309,39 @@ kubectl create clusterrolebinding NAME --clusterrole cluster-admin --user <YOUR_
13091309
```
13101310
13111311
### Docker cache support for GKE
1312-
1312+
##### Local SSD
13131313
If you want to use *LocalSSD* in GKE:
13141314
1315-
*Prerequisite:* [GKE cluster with local SSD](https://cloud.google.com/kubernetes-engine/docs/how-to/persistent-volumes/local-ssd)
1315+
*Prerequisites:* [GKE cluster with local SSD](https://cloud.google.com/kubernetes-engine/docs/how-to/persistent-volumes/local-ssd)
13161316
1317-
*Install runner using GKE Local SSD:*
1317+
Install runner using GKE Local SSD:
13181318
```
13191319
codefresh runner init[options] --set-value=Storage.LocalVolumeParentDir=/mnt/disks/ssd0/codefresh-volumes\
13201320
--build-node-selector=cloud.google.com/gke-local-ssd=true
13211321
```
13221322
1323+
`values-example.yaml`
1324+
{% highlight yaml %}
1325+
{% raw %}
1326+
...
1327+
### Storage parameters example for gke-local-ssd
1328+
Storage:
1329+
Backend: local
1330+
LocalVolumeParentDir: /mnt/disks/ssd0/codefresh-volumes
1331+
NodeSelector: cloud.google.com/gke-local-ssd=true
1332+
...
1333+
Runtime:
1334+
NodeSelector: # dind and engine pods node-selector (--build-node-selector)
1335+
cloud.google.com/gke-local-ssd: "true"
1336+
...
1337+
{% endraw %}
1338+
{% endhighlight %}
1339+
1340+
To configure existing Runner with Local SSD follow this article:
1341+
1342+
[How-to: Configuring an existing Runtime Environment with Local SSDs (GKE only)](https://support.codefresh.io/hc/en-us/articles/360016652920-How-to-Configuring-an-existing-Runtime-Environment-with-Local-SSDs-GKE-only-)
1343+
1344+
##### GCE Disks
13231345
If you want to use *GCE Disks*:
13241346
13251347
*Prerequisite:* volume provisioner (dind-volume-provisioner) should have permissions to create/delete/get of Google disks
@@ -1332,7 +1354,7 @@ There are 3 options to provide cloud credentials on GCE:
13321354
13331355
Notice that builds will be running in a single availability zone, so you must specify AvailabilityZone parameters.
13341356
1335-
Install Runner usingGKE Disks:
1357+
Install Runner usingGCE Disks:
13361358
13371359
```
13381360
codefresh runner init[options] --set-value=Storage.Backend=gcedisk\
@@ -1341,6 +1363,41 @@ codefresh runner init [options] --set-value=Storage.Backend=gcedisk \
13411363
[--set-file=Storage.GoogleServiceAccount=/path/to/google-service-account.json]
13421364
```
13431365
1366+
`values-example.yaml`
1367+
{% highlight yaml %}
1368+
{% raw %}
1369+
...
1370+
### Storage parameter example for GCE disks
1371+
Storage:
1372+
Backend: gcedisk
1373+
AvailabilityZone: us-central1-c
1374+
GoogleServiceAccount: > #serviceAccount.json content
1375+
{
1376+
"type": "service_account",
1377+
"project_id": "...",
1378+
"private_key_id": "...",
1379+
"private_key": "...",
1380+
"client_email": "...",
1381+
"client_id": "...",
1382+
"auth_uri": "...",
1383+
"token_uri": "...",
1384+
"auth_provider_x509_cert_url": "...",
1385+
"client_x509_cert_url": "..."
1386+
}
1387+
NodeSelector: failure-domain.beta.kubernetes.io/zone=us-central1-c
1388+
...
1389+
Runtime:
1390+
NodeSelector: # dind and engine pods node-selector (--build-node-selector)
1391+
failure-domain.beta.kubernetes.io/zone: us-central1-c
1392+
...
1393+
{% endraw %}
1394+
{% endhighlight %}
1395+
1396+
To configure existing Runner with GCE disks follow this article:
1397+
1398+
[How-to: Configuring an existing Runtime Environment with GCE disks](https://support.codefresh.io/hc/en-us/articles/360016652900-How-to-Configuring-an-existing-Runtime-Environment-with-GCE-disks)
1399+
1400+
13441401
#### Using multiple Availability Zones
13451402
13461403
Currently, to support effective caching with GCE disks, the builds/pods need to be scheduled in a single AZ (this is more related to a GCP limitation than a Codefresh runner issue).

0 commit comments

Comments
 (0)
[8]ページ先頭
©2009-2025 Movatter.jp