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
Copy file name to clipboardExpand all lines: charts/gitops-runtime/README.md
+66-4Lines changed: 66 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -15,6 +15,68 @@ See [Use OCI-based registries](https://helm.sh/docs/topics/registries/)
15
15
## Codefresh official documentation:
16
16
Prior to running the installation please see the official documentation at: https://codefresh.io/docs/docs/installation/gitops/hybrid-gitops-helm-installation/
17
17
18
+
## Multi Runtime Installation
19
+
You can install multiple Codefresh GitOps Runtimes in the same cluster, as long as each Runtime is deployed in its own namespace and manages only the applications in that namespace.
20
+
To achieve this, configure your Runtimes to run in namespaced mode by setting `global.runtime.singleNamespace=true`. See the values.yaml example below:
21
+
```yaml
22
+
global:
23
+
runtime:
24
+
singleNamespace: true
25
+
sealed-secrets:
26
+
enabled: false
27
+
argo-cd:
28
+
createClusterRoles: false
29
+
crds:
30
+
install: false
31
+
configs:
32
+
params:
33
+
application.namespaces: ''
34
+
argo-events:
35
+
controller:
36
+
rbac:
37
+
namespaced: true
38
+
argo-workflows:
39
+
crds:
40
+
install: false
41
+
singleNamespace: true
42
+
createAggregateRoles: false
43
+
controller:
44
+
clusterWorkflowTemplates:
45
+
enabled: false
46
+
server:
47
+
clusterWorkflowTemplates:
48
+
enabled: false
49
+
argo-rollouts:
50
+
enabled: false
51
+
tunnel-client:
52
+
enabled: false
53
+
gitops-operator:
54
+
crds:
55
+
install: false
56
+
```
57
+
58
+
Note that for the first runtime in the cluster, you have to configure it to install the CRDs, with setting these values:
59
+
```yaml
60
+
global:
61
+
runtime:
62
+
isConfigurationRuntime: true
63
+
argo-cd:
64
+
crds:
65
+
install: true
66
+
argo-workflows:
67
+
crds:
68
+
install: true
69
+
argo-rollouts:
70
+
installCRDs: true
71
+
gitops-operator:
72
+
crds:
73
+
install: true
74
+
```
75
+
76
+
> [!WARNING]
77
+
> If you want more than one runtime in your cluster, make sure that all of the runtimes in your cluster are configured with `global.runtime.singleNamespace=true`.
78
+
> If you already have a runtime installed in the cluster without this setting, multi runtime installation is not supported.
79
+
18
80
## Argo-workflows artifact and log storage
19
81
Codefresh provides a SaaS object storage based solution for Argo workflows logs storage. The chart deploys a configmap named `codefresh-workflows-log-store` with the repository configuration.
20
82
If you want to utilize the Codefresh SaaS solution for log storage for all workflows in the runtime please set the following values:
@@ -415,6 +477,7 @@ gitops-operator:
415
477
| event-reporters.workflow.sensor.tolerations | list | `[]` | |
| gitops-operator.config.maxConcurrentReleases | int | `100` | Maximum number of concurrent releases being processed by the operator (this will not affect the number of releases being processed by the gitops runtime) |
420
483
| gitops-operator.config.promotionWrapperTemplate | string | `""` | An optional template for the promotion wrapper (empty default will use the embedded one) |
@@ -427,9 +490,7 @@ gitops-operator:
427
490
| gitops-operator.crds.keep | bool | `false` | Keep CRDs if gitops runtime release is uninstalled |
| global.runtime.ingressUrl | string | `""` | Explicit url for runtime ingress. Provide this value only if you don't want the chart to create and ingress (global.runtime.ingress.enabled=false) and tunnel-client is not used (tunnel-client.enabled=false) |
504
565
| global.runtime.isConfigurationRuntime | bool | `false` | is the runtime set as a "configuration runtime". |
505
566
| global.runtime.name | string | `nil` | Runtime name. Must be unique per platform account. |
567
+
| global.runtime.singleNamespace | bool | `false` | Runtime single namespace mode. When true, runtime operates in single namespace scope. |
506
568
| global.tolerations | list | `[]` | Global tolerations for all components |
507
569
| installer | object | `{"affinity":{},"argoCdVersionCheck":{"argoServerLabels":{"app.kubernetes.io/component":"server","app.kubernetes.io/part-of":"argocd"}},"image":{"pullPolicy":"IfNotPresent","repository":"quay.io/codefresh/gitops-runtime-installer","tag":""},"nodeSelector":{},"skipUsageValidation":false,"skipValidation":false,"tolerations":[]}` | Runtime installer used for running hooks and checks on the release |
508
570
| installer.skipUsageValidation | bool | `false` | if set to true, pre-install hook will *not* run |
Copy file name to clipboardExpand all lines: charts/gitops-runtime/README.md.gotmpl
+63Lines changed: 63 additions & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -15,6 +15,69 @@ See [Use OCI-based registries](https://helm.sh/docs/topics/registries/)
15
15
## Codefresh official documentation:
16
16
Prior to running the installation please see the official documentation at: https://codefresh.io/docs/docs/installation/gitops/hybrid-gitops-helm-installation/
17
17
18
+
## Multi Runtime Installation
19
+
You can install multiple Codefresh GitOps Runtimes in the same cluster, as long as each Runtime is deployed in its own namespace and manages only the applications in that namespace.
20
+
To achieve this, configure your Runtimes to run in namespaced mode by setting `global.runtime.singleNamespace=true`. See the values.yaml example below:
21
+
```yaml
22
+
global:
23
+
runtime:
24
+
singleNamespace: true
25
+
sealed-secrets:
26
+
enabled: false
27
+
argo-cd:
28
+
createClusterRoles: false
29
+
crds:
30
+
install: false
31
+
configs:
32
+
params:
33
+
application.namespaces: ''
34
+
argo-events:
35
+
controller:
36
+
rbac:
37
+
namespaced: true
38
+
argo-workflows:
39
+
crds:
40
+
install: false
41
+
singleNamespace: true
42
+
createAggregateRoles: false
43
+
controller:
44
+
clusterWorkflowTemplates:
45
+
enabled: false
46
+
server:
47
+
clusterWorkflowTemplates:
48
+
enabled: false
49
+
argo-rollouts:
50
+
enabled: false
51
+
tunnel-client:
52
+
enabled: false
53
+
gitops-operator:
54
+
crds:
55
+
install: false
56
+
```
57
+
58
+
Note that for the first runtime in the cluster, you have to configure it to install the CRDs, with setting these values:
59
+
```yaml
60
+
global:
61
+
runtime:
62
+
isConfigurationRuntime: true
63
+
argo-cd:
64
+
crds:
65
+
install: true
66
+
argo-workflows:
67
+
crds:
68
+
install: true
69
+
argo-rollouts:
70
+
installCRDs: true
71
+
gitops-operator:
72
+
crds:
73
+
install: true
74
+
```
75
+
76
+
> [!WARNING]
77
+
> If you want more than one runtime in your cluster, make sure that all of the runtimes in your cluster are configured with `global.runtime.singleNamespace=true`.
78
+
> If you already have a runtime installed in the cluster without this setting, multi runtime installation is not supported.
79
+
80
+
18
81
## Argo-workflows artifact and log storage
19
82
Codefresh provides a SaaS object storage based solution for Argo workflows logs storage. The chart deploys a configmap named `codefresh-workflows-log-store` with the repository configuration.
20
83
If you want to utilize the Codefresh SaaS solution for log storage for all workflows in the runtime please set the following values:
0 commit comments