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
chore: remove argo-rollouts from gitops-runtime helm chart
Argo Rollouts was deprecated and disabled by default in a previous release.
This commit completes the removal by:
- Removing argo-rollouts dependency from Chart.yaml
- Removing external-argo-rollouts and argo-rollouts configuration from values.yaml
- Removing argo-rollouts helper function and component-list entry from _helpers.tpl
- Removing ROLLOUTS_HELM_REPOSITORY/VERSION env vars from app-proxy
- Removing argo-rollouts from all CI values files
- Removing argo-rollouts from multi-runtime values files
- Removing argo-rollouts tests and rollout-reporter references
- Updating README documentation to remove argo-rollouts sections
- Removing rollout-reporter from values-ha.yaml
BREAKING CHANGE: argo-rollouts is no longer included in the chart.
Users requiring Argo Rollouts must install it separately.
Copy file name to clipboardExpand all lines: charts/gitops-runtime/README.md
-32Lines changed: 0 additions & 32 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -8,7 +8,6 @@
8
8
-[Codefresh official documentation](#codefresh-official-documentation)
9
9
-[Argo-workflows artifact and log storage](#argo-workflows-artifact-and-log-storage)
10
10
-[Installation with External ArgoCD](#installation-with-external-argocd)
11
-
-[Installation with External Argo Rollouts](#installation-with-external-argo-rollouts)
12
11
-[Using with private registries - Helper utility](#using-with-private-registries---helper-utility)
13
12
-[Openshift](#openshift)
14
13
-[High Availability](#high-availability)
@@ -62,8 +61,6 @@ argo-workflows:
62
61
server:
63
62
clusterWorkflowTemplates:
64
63
enabled: false
65
-
argo-rollouts:
66
-
enabled: false
67
64
tunnel-client:
68
65
enabled: false
69
66
gitops-operator:
@@ -82,8 +79,6 @@ argo-cd:
82
79
argo-workflows:
83
80
crds:
84
81
install: true
85
-
argo-rollouts:
86
-
installCRDs: true
87
82
gitops-operator:
88
83
crds:
89
84
install: true
@@ -191,26 +186,6 @@ data:
191
186
admin.enabled: "true"
192
187
```
193
188
194
-
## Installation with External Argo Rollouts
195
-
196
-
If you want to use an existing Argo Rollouts installation, you can disable the built-in Argo Rollouts and configure the GitOps Runtime to use the external Argo Rollouts.
197
-
See the `values.yaml` example below:
198
-
199
-
```yaml
200
-
global:
201
-
# -- Configuration for external Argo Rollouts
202
-
external-argo-rollouts:
203
-
# -- Rollout reporter settings
204
-
rollout-reporter:
205
-
# -- Enable rollout reporter
206
-
# Configuration is defined at .Values.event-reporters.rollout
207
-
enabled: true
208
-
209
-
argo-rollouts:
210
-
# -- Disable built-in Argo Rollouts
211
-
enabled: false
212
-
```
213
-
214
189
## Using with private registries - Helper utility
215
190
The GitOps Runtime comprises multiple subcharts and container images. Subcharts also vary in values structure, making it difficult to override image specific values to use private registries.
216
191
We have created a helper utility to resolve this issue:
| argo-gateway | object | `{"affinity":{},"hpa":{"enabled":true,"maxReplicas":10,"minReplicas":1,"targetCPUUtilizationPercentage":70},"image":{"registry":"quay.io","repository":"codefresh/cf-argocd-extras","tag":"d4fefcb"},"livenessProbe":{"failureThreshold":3,"initialDelaySeconds":10,"periodSeconds":10,"successThreshold":1,"timeoutSeconds":10},"nodeSelector":{},"pdb":{"enabled":true,"maxUnavailable":"","minAvailable":"50%"},"readinessProbe":{"failureThreshold":3,"initialDelaySeconds":10,"periodSeconds":10,"successThreshold":1,"timeoutSeconds":10},"resources":{"requests":{"cpu":"100m","memory":"128Mi"}},"service":{"type":"ClusterIP"},"serviceAccount":{"create":true},"serviceMonitor":{"enabled":false,"interval":"30s","labels":{},"scrapeTimeout":"10s"},"tolerations":[]}` | Argo Gateway Argo Gateway is used to perform operations on ArgoCD from Codefresh platform |
605
-
| argo-rollouts.controller.replicas | int | `1` | |
| global.codefresh.userToken.secretKeyRef | object | `{}` | User token that references an existing secret containing the token. |
666
637
| global.codefresh.userToken.token | string | `""` | User token in plain text. The chart creates and manages the secret for this token. |
667
638
| global.event-reporters | object | `{"affinity":{},"config":{},"image":{"registry":"quay.io","repository":"codefresh/cf-argocd-extras","tag":"d4fefcb"},"livenessProbe":{"failureThreshold":3,"initialDelaySeconds":10,"periodSeconds":10,"successThreshold":1,"timeoutSeconds":10},"nodeSelector":{},"pdb":{"enabled":true,"maxUnavailable":"","minAvailable":"50%"},"readinessProbe":{"failureThreshold":3,"initialDelaySeconds":10,"periodSeconds":10,"successThreshold":1,"timeoutSeconds":10},"replicaCount":2,"resources":{"requests":{"cpu":"100m","memory":"128Mi"}},"service":{"ports":{"http":{"port":8088,"targetPort":8088},"metrics":{"port":8087,"targetPort":8087}},"type":"ClusterIP"},"serviceAccount":{"create":true},"serviceMonitor":{"enabled":false,"interval":"30s","labels":{},"scrapeTimeout":"10s"},"tolerations":[]}` | Global settings for event reporters Event reporters are used for reporting runtime and cluster resources to Codefresh platform |
| global.external-argo-rollouts.rollout-reporter.enabled | bool | `false` | Enable or disable rollout reporter Configuration is defined at .Values.event-reporters.rollout |
671
639
| global.httpProxy | string | `""` | global HTTP_PROXY for all components |
672
640
| global.httpsProxy | string | `""` | global HTTPS_PROXY for all components |
Copy file name to clipboardExpand all lines: charts/gitops-runtime/README.md.gotmpl
-25Lines changed: 0 additions & 25 deletions
Original file line number
Diff line number
Diff line change
@@ -8,7 +8,6 @@
8
8
- [Codefresh official documentation](#codefresh-official-documentation)
9
9
- [Argo-workflows artifact and log storage](#argo-workflows-artifact-and-log-storage)
10
10
- [Installation with External ArgoCD](#installation-with-external-argocd)
11
-
- [Installation with External Argo Rollouts](#installation-with-external-argo-rollouts)
12
11
- [Using with private registries - Helper utility](#using-with-private-registries---helper-utility)
13
12
- [Openshift](#openshift)
14
13
- [High Availability](#high-availability)
@@ -62,8 +61,6 @@ argo-workflows:
62
61
server:
63
62
clusterWorkflowTemplates:
64
63
enabled: false
65
-
argo-rollouts:
66
-
enabled: false
67
64
tunnel-client:
68
65
enabled: false
69
66
gitops-operator:
@@ -82,8 +79,6 @@ argo-cd:
82
79
argo-workflows:
83
80
crds:
84
81
install: true
85
-
argo-rollouts:
86
-
installCRDs: true
87
82
gitops-operator:
88
83
crds:
89
84
install: true
@@ -194,26 +189,6 @@ data:
194
189
admin.enabled: "true"
195
190
```
196
191
197
-
## Installation with External Argo Rollouts
198
-
199
-
If you want to use an existing Argo Rollouts installation, you can disable the built-in Argo Rollouts and configure the GitOps Runtime to use the external Argo Rollouts.
200
-
See the `values.yaml` example below:
201
-
202
-
```yaml
203
-
global:
204
-
# -- Configuration for external Argo Rollouts
205
-
external-argo-rollouts:
206
-
# -- Rollout reporter settings
207
-
rollout-reporter:
208
-
# -- Enable rollout reporter
209
-
# Configuration is defined at .Values.event-reporters.rollout
210
-
enabled: true
211
-
212
-
argo-rollouts:
213
-
# -- Disable built-in Argo Rollouts
214
-
enabled: false
215
-
```
216
-
217
192
## Using with private registries - Helper utility
218
193
The GitOps Runtime comprises multiple subcharts and container images. Subcharts also vary in values structure, making it difficult to override image specific values to use private registries.
219
194
We have created a helper utility to resolve this issue:
0 commit comments