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

Commit89470d4

Browse files
fix on-prem example
1 parentc74c6c9 commit89470d4

File tree

2 files changed

+44
-58
lines changed

2 files changed

+44
-58
lines changed

‎_docs/administration/codefresh-on-prem.md‎

Lines changed: 14 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -622,7 +622,7 @@ postgresql:
622622

623623
If you would prefer running the seed job manually, you can do it by using a script present in `your/stage-dir/codefresh/addons/seed-scripts` directory named `postgres-seed.sh`. The script takes the following set of variables that you need to have set before running it:
624624

625-
```sh
625+
```shell
626626
export POSTGRES_SEED_USER="postgres"
627627
export POSTGRES_SEED_PASSWORD="zDyGp79XyZEqLq7V"
628628
export POSTGRES_USER="cf_user"
@@ -637,10 +637,10 @@ However you **still need to specify a set of values** in the Codefresh config fi
637637

638638
```yaml
639639
global:
640-
postgresUser:<POSTGRES_USER>
641-
postgresPassword:<POSTGRES_PASSWORD>
640+
postgresUser:cf_user
641+
postgresPassword:fJTFJMGV7sg5E4Bj
642642
postgresDatabase: codefresh
643-
postgresHostname:<POSTGRES_HOST>
643+
postgresHostname:my-postgresql.prod.svc.cluster.local
644644
postgresPort: 5432
645645
646646
postgresql:
@@ -705,20 +705,23 @@ mongo:
705705
### Configure an external Redis service
706706
Codefresh recommends to use the Bitnami Redis [chart](https://github.com/bitnami/charts/tree/master/bitnami/redis) as a Redis store.
707707

708-
#### Limitations
708+
**Limitations**
709+
709710
Codefresh does not support secure connection to Redis (TLS) and AUTH username extension.
710711

711-
#### Configuration
712-
To configure Codefresh to use an external Redis service, add the following parameters to your __config.yaml__:
712+
**Configuration**
713+
714+
To configure Codefresh to use an external Redis service, add the following parameters to your `config.yaml`:
713715

716+
`config.yaml` example:
714717
```yaml
715718
global:
716-
redisUrl: <REDIS_HOST>
717-
redisPassword: <REDIS_PASS>
719+
redisUrl: my-redis.prod.svc.cluster.local
718720
redisPort: 6379
721+
redisPassword: 6oOhHI8fI5
719722
720-
runtimeRedisHost:<REDIS_HOST>
721-
runtimeRedisPassword:<REDIS_PASS>
723+
runtimeRedisHost:my-redis.prod.svc.cluster.local
724+
runtimeRedisPassword:6oOhHI8fI5
722725
runtimeRedisPort: 6379
723726
runtimeRedisDb: 2
724727

‎_docs/administration/codefresh-runner.md‎

Lines changed: 30 additions & 47 deletions
Original file line numberDiff line numberDiff line change
@@ -1164,25 +1164,27 @@ If you are installing Codefresh runner on the Kubernetes cluster on [GKE](https:
11641164
* bind your user with `cluster-admin` Kubernetes cluster role.
11651165
11661166
```shell
1167-
kubectl create clusterrolebinding NAME --clusterrole cluster-admin --user <YOUR_USER>
1167+
kubectl create clusterrolebinding cluster-admin-binding \
1168+
--clusterrole cluster-admin \
1169+
--user $(gcloud config get-value account)
11681170
```
11691171
1170-
### Docker cache support for GKE
1172+
#### Storage options on GKE
11711173
1172-
####Local SSD
1174+
**Local SSD**
11731175
11741176
If you want to use *LocalSSD* in GKE:
11751177
11761178
*Prerequisites:* [GKE cluster with local SSD](https://cloud.google.com/kubernetes-engine/docs/how-to/persistent-volumes/local-ssd)
11771179
1178-
Install Runnerusing GKE Local SSD:
1180+
Install Runnerwith the Wizard:
11791181
11801182
```shell
11811183
codefresh runner init [options] --set-value=Storage.LocalVolumeParentDir=/mnt/disks/ssd0/codefresh-volumes \
11821184
--build-node-selector=cloud.google.com/gke-local-ssd=true
11831185
```
11841186
1185-
`values-example.yaml`
1187+
Or with`values-example.yaml` values file:
11861188
11871189
```yaml
11881190
...
@@ -1197,18 +1199,21 @@ codefresh runner init [options] --set-value=Storage.LocalVolumeParentDir=/mnt/di
11971199
cloud.google.com/gke-local-ssd: "true"
11981200
...
11991201
```
1202+
```shell
1203+
codefresh runner init [options] --values values-example.yaml
1204+
```
12001205
12011206
To configure existing Runner with Local SSDs follow this article:
12021207
12031208
[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-)
12041209
1205-
####GCE Disks
1210+
**GCE Disks**
12061211
12071212
If you want to use *GCE Disks*:
12081213
12091214
*Prerequisites:* volume provisioner (dind-volume-provisioner) should have permissions to create/delete/get GCE disks
12101215
1211-
There are 3 options to provide cloud credentials on GCE:
1216+
There are 3 options to provide cloud credentials:
12121217
12131218
* run `dind-volume-provisioner-runner` pod on a node with IAM role which is allowed to create/delete/get GCE disks
12141219
* create Google Service Account with `ComputeEngine.StorageAdmin` role, download its key in JSON format and pass it to `codefresh runner init` with `--set-file=Storage.GooogleServiceAccount=/path/to/google-service-account.json`
@@ -1229,9 +1234,7 @@ codefresh runner init [options] \
12291234
--set-file=Storage.GoogleServiceAccount=/path/to/google-service-account.json
12301235
```
12311236
1232-
Using the values file:
1233-
`values-example.yaml`
1234-
1237+
Using the values `values-example.yaml` file:
12351238
```yaml
12361239
...
12371240
### Storage parameter example for GCE disks
@@ -1258,14 +1261,13 @@ Using the values file:
12581261
topology.kubernetes.io/zone: us-central1-c
12591262
...
12601263
```
1261-
12621264
```shell
12631265
codefresh runner init [options] --values values-example.yaml
12641266
```
12651267
12661268
##### Runner installation with GCE Disks (Workload Identity with IAM role)
12671269
1268-
`values-example.yaml`
1270+
Using the values`values-example.yaml` file:
12691271
12701272
```yaml
12711273
...
@@ -1284,6 +1286,9 @@ codefresh runner init [options] --values values-example.yaml
12841286
topology.kubernetes.io/zone: us-central1-c
12851287
...
12861288
```
1289+
```shell
1290+
codefresh runner init [options] --values values-example.yaml
1291+
```
12871292
12881293
Create the binding between Kubernetes service account and Google service account:
12891294
@@ -1311,59 +1316,37 @@ If you have Kubernetes nodes running in multiple Availability Zones and wish to
13111316
13121317
**Option A** - Provision a new Kubernetes cluster: a cluster that runs in a single AZ only. - The cluster should be dedicated for usage with the Codefresh runner. This is the preferred solution and avoids extra complexity.
13131318
1314-
**Option B** - Install Codefresh runner in your multi-zone cluster, and let it run in the default Node Pool: - in this case, you must specify `--build-node-selector=<node-az-label>` (e.g.: `--build-node-selector=failure-domain.beta.kubernetes.io/zone=us-central1-a`) or simply modify the Runtime environment as below:
1319+
**Option B** - Install Codefresh runner in your multi-zone cluster, and let it run in the default Node Pool: - in this case, you must specify `--build-node-selector=<node-az-label>` (e.g.: `--build-node-selector=topology.kubernetes.io/zone=us-central1-c`) or simply modify the Runtime environment as below:
13151320
13161321
```shell
1317-
codefresh getruntime-environments gke_us-east4_my-gke-cluster/codefresh -o yaml > re.yaml
1322+
codefresh getre $RUNTIME_NAME -o yaml > re.yaml
13181323
```
13191324
13201325
Edit the yaml:
13211326
13221327
```yaml
1323-
version: 2metadata:
1324-
agent: true
1325-
trial:
1326-
endingAt: 34534534
1327-
reason: Codefresh hybrid runtime
1328-
started: 23434
1329-
name: gke_us-east4_my-gke-cluster/codefresh
1330-
changedBy: kostis
1331-
creationTime:'2020/04/01 21:04:11'
1328+
version: 2
1329+
metadata:
1330+
...
13321331
runtimeScheduler:
13331332
cluster:
1334-
clusterProvider:
1335-
accountId: 34543545456
1336-
selector: gke_us-east4_my-gke-cluster
1337-
namespace: codefresh
1338-
nodeSelector:
1339-
failure-domain.beta.kubernetes.io/zone: us-east4-a
1333+
nodeSelector: #schedule engine pod onto a node whose labels match the nodeSelector
1334+
topology.kubernetes.io/zone: us-central1-c
1335+
...
13401336
dockerDaemonScheduler:
13411337
cluster:
1342-
clusterProvider:
1343-
accountId: 5cdd8937242f167387e5aa56
1344-
selector: gke_us-east4_my-gke-cluster
1345-
namespace: codefresh
1346-
nodeSelector:
1347-
failure-domain.beta.kubernetes.io/zone: us-east4-a
1348-
dockerDaemonParams: null
1338+
nodeSelector: #schedule dind pod onto a node whose labels match the nodeSelector
1339+
topology.kubernetes.io/zone: us-central1-c
1340+
...
13491341
pvcs:
13501342
dind:
1351-
storageClassName: dind-gcedisk-us-east4-a-venona-codefresh
1352-
reuseVolumeSelector:'codefresh-app,io.codefresh.accountName,pipeline_id'
1353-
volumeSize: 30Gi
1354-
userAccess: true
1355-
extends:
1356-
- system/default/hybrid/k8s
1357-
description: >-
1358-
Runtime environment configure to cluster:
1359-
gke_us-east4_my-gke-cluster and namespace: codefresh
1360-
accountId: 45645k694353459
1343+
...
13611344
```
13621345
13631346
Apply changes with:
13641347
13651348
```shell
1366-
codefresh patchruntime-environments -f re.yaml
1349+
codefresh patchre -f re.yaml
13671350
```
13681351
13691352
**Option C** - Like option B, but with a dedicated Node Pool

0 commit comments

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