@@ -283,7 +283,7 @@ There are three options for this:
283283
284284#### Configuration
285285
286- 1. Create Storage Class for EBS volumes:
286+ **Step 1:** Create Storage Class for EBS volumes:
287287 >Choose **one** of the Availability Zones (AZs)to be used for your pipeline builds. Multi AZ configuration is not supported.
288288
289289 * **Storage Class (gp2)**
@@ -334,28 +334,25 @@ parameters:
334334 # Max - 1000.
335335 throughput: "500"
336336` ` `
337- {:start=" 2" }
338- 1. Apply storage class manifest:
337+ **Step 2:** Apply storage class manifest:
339338` ` ` shell
340339kubectl apply -f dind-ebs.yaml
341340` ` `
342- {:start=" 3" }
343- 1. Get the YAML representation of the runtime you just added:
344- * Get a list of all available runtimes:
345- ` ` ` shell
346- codefresh get runtime-environments
347- ` ` `
348- * Select the runtime you just added, and get its YAML representation:
341+ **Step 3:** Get the YAML representation of the runtime you just added:
342+ * Get a list of all available runtimes:
343+ ` ` ` shell
344+ codefresh get runtime-environments
345+ ` ` `
346+ * Select the runtime you just added, and get its YAML representation:
349347` ` ` shell
350348codefresh get runtime-environments my-eks-cluster/codefresh -o yaml> runtime.yaml
351349` ` `
352- {:start=" 4" }
353- 1. Modify the YAML:
350+ **Step 4:** Modify the YAML:
354351 * In` dockerDaemonScheduler.cluster` , add` nodeSelector: topology.kubernetes.io/zone:< your_az_here> ` .
355352 > Make sure you define the same AZ you selected for Runtime Configuration.
356353 * Modify` pvcs.dind` to use the Storage Class you created above (` dind-ebs` ).
357354
358- Here is an example of the` runtime.yaml` including the required updates:
355+ Here is an example of the` runtime.yaml` including the required updates:
359356` ` ` yaml
360357version: 1
361358metadata:
@@ -391,19 +388,16 @@ extends:
391388description:' ...'
392389accountId: 5f048d85eb107d52b16c53ea
393390` ` `
394- {:start=" 5" }
395- 1. Update your runtime environment with the [patch command](https://codefresh-io.github.io/cli/operate-on-resources/patch/):
391+ **Step 5:** Update your runtime environment with the [patch command](https://codefresh-io.github.io/cli/operate-on-resources/patch/):
396392` ` ` shell
397393codefresh patch runtime-environment my-eks-cluster/codefresh -f runtime.yaml
398394` ` `
399- {:start=" 6" }
400- 1. If necessary, delete all existing PV (Persistent Volume) and PVC (Persistent Volume Claim ) objects that remain from the default local provisioner:
395+ **Step 6:** If necessary, delete all existing PV (Persistent Volume) and PVC (Persistent Volume Claim ) objects that remain from the default local provisioner:
401396` ` `
402397kubectl delete pvc -l codefresh-app=dind -n< your_runner_ns>
403398kubectl delete pv -l codefresh-app=dind -n< your_runner_ns>
404399` ` `
405- {:start=" 7" }
406- 1. Restart the volume provisioner pod.
400+ **Step 7:** Restart the volume provisioner pod.
407401
408402##### Values YAML for configuration
409403>You can define all these options above for clean Runner installation with [values.yaml](https://github.com/codefresh-io/venona/blob/release-1.0/venonactl/example/values-example.yaml){:target=" \_ blank" } file: