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
**Step 6:** If necessary, delete all existing PV (Persistent Volume) and PVC (Persistent Volume Claim ) objects that remain from the default local provisioner:
@@ -1232,18 +1238,20 @@ Once the cluster is up and running, install the [cluster autoscaler](https://doc
1232
1238
1233
1239
Because we used IAM AddonPolicies`"autoScaler: true"` in the`cluster.yaml` file, everything is done automatically, and there is no need to create a separate IAM policy or add Auto Scaling group tags.
If the version of the EKS cluster 1.15, the corresponding autoscaler version according to [https://github.com/kubernetes/autoscaler/releases](https://github.com/kubernetes/autoscaler/releases){:target="\_blank"} is 1.15.6.
#### Step 4: Add an EKS cluster as Runner to the Codefresh platform with EBS support
1286
1295
1296
+
**How to**
1297
+
1287
1298
1. Make sure target the correct cluster:
1299
+
1288
1300
```shell
1289
1301
$ kubectl config current-context
1290
1302
my-aws-runner
@@ -1309,13 +1321,16 @@ codefresh runner init \
1309
1321
--set-value=Storage.KmsKeyId=<key id>
1310
1322
```
1311
1323
For descriptions of the other options, run`codefresh runner init --help` ([global parameter table](#customizing-the-wizard-installation)).
1324
+
1312
1325
{:start="3"}
1313
1326
1. When the Wizard completes the installation, modify the runtime environment of`my-aws-runner` to specify the necessary toleration, nodeSelector and disk size:
1314
-
* Run:
1327
+
* Run:
1328
+
1315
1329
```shell
1316
1330
codefresh get re --limit=100 my-aws-runner/cf -o yaml> my-runtime.yml
1317
1331
```
1318
1332
* Modify the file`my-runtime.yml` as shown below:
1333
+
1319
1334
```yaml
1320
1335
version: null
1321
1336
metadata:
@@ -1368,6 +1383,7 @@ extends:
1368
1383
description:'Runtime environment configure to cluster: my-aws-runner and namespace: cf'
1369
1384
accountId: 5cb563d0506083262ba1f327
1370
1385
```
1386
+
1371
1387
{:start="4"}
1372
1388
1. Apply changes.
1373
1389
```shell
@@ -1542,12 +1558,14 @@ Once complete, you can go to the Codefresh UI and run a pipeline on the new runt
1542
1558
Depending on your Rancher configuration, you may need to allow insecure HTTPS/TLS connections, by adding an environment variable to the Runner deployment.
1543
1559
1544
1560
* Edit the Runner deployment:
1545
-
The example below assumes that you installed the Runner in the`codefresh` namespace.
1561
+
The example below assumes that you installed the Runner in the`codefresh` namespace.
1562
+
1546
1563
```shell
1547
1564
kubectl edit deploy runner -n codefresh
1548
1565
```
1549
1566
1550
-
* In the editor, add this environment variable below`spec.containers.env[]`:
1567
+
* In the editor, add this environment variable below`spec.containers.env[]`:
1568
+
1551
1569
```yaml
1552
1570
- name: NODE_TLS_REJECT_UNAUTHORIZED
1553
1571
value:"0"
@@ -1602,6 +1620,7 @@ az role assignment create --assignee $NODE_SERVICE_PRINCIPAL --scope /subscripti