Notice that builds will be running in a single availability zone, so you must specify AvailabilityZone parameters.

Install Runner using GCE Disks:

Using the Wizard:

codefresh runner init [options] \

--set-value=Storage.Backend=gcedisk \

--set-value=Storage.AvailabilityZone=us-central1-c \

--kube-node-selector=topology.kubernetes.io/zone=us-central1-c \

--build-node-selector=topology.kubernetes.io/zone=us-central1-c \

--set-file=Storage.GoogleServiceAccount=/path/to/google-service-account.json

Using the values file:

{% highlight yaml %}

{% raw %}

"auth_provider_x509_cert_url": "...",

"client_x509_cert_url": "..."

}

NodeSelector:failure-domain.beta.kubernetes.io/zone=us-central1-c

NodeSelector:topology.kubernetes.io/zone=us-central1-c

...

Runtime:

NodeSelector: # dind and engine pods node-selector (--build-node-selector)

failure-domain.beta.kubernetes.io/zone: us-central1-c

topology.kubernetes.io/zone: us-central1-c

...

{% endraw %}

{% endhighlight %}

codefresh runner init [options] --values values-example.yaml

{% highlight yaml %}

{% raw %}

...

Storage:

Backend: gcedisk

AvailabilityZone: us-central1-c

VolumeProvisioner:

ServiceAccount:

Annotations: #annotation to the volume-provisioner service account, using the email address of the Google service account

iam.gke.io/gcp-service-account: <GSA_NAME>@<PROJECT_ID>.iam.gserviceaccount.com

NodeSelector: topology.kubernetes.io/zone=us-central1-c

...

Runtime:

NodeSelector: # dind and engine pods node-selector (--build-node-selector)

topology.kubernetes.io/zone: us-central1-c

...

{% endraw %}

{% endhighlight %}

Create the binding between Kubernetes service account and Google service account:

export K8S_NAMESPACE=codefresh

export KSA_NAME=volume-provisioner-runner

export GSA_NAME=<google_sa_name>

export PROJECT_ID=<google_project_name>

gcloud iam service-accounts add-iam-policy-binding \

--role roles/iam.workloadIdentityUser \

--member"serviceAccount:${PROJECT_ID}.svc.id.goog[${K8S_NAMESPACE}/${KSA_NAME}]" \

${GSA_NAME}@${PROJECT_ID}.iam.gserviceaccount.com

To configure existing Runner with GCE Disks follow this article:

[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)

- Custom plugins can be used in hooks -[documentation]({{site.baseurl}}/docs/codefresh-yaml/hooks/#limitations-of-pipelinestep-hooks)

- Variables can now be used in hooks -[documentation]({{site.baseurl}}/docs/codefresh-yaml/hooks/#limitations-of-pipelinestep-hooks)

- New`CF_STEP_NAME` variable -[documentation]({{site.baseurl}}/docs/codefresh-yaml/variables/#system-provided-variables)

- Update Runner for GCE Disks -[documentation]({{site.baseurl}}/docs/administration/codefresh-runner/#docker-cache-support-for-gke)