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(argocd-image-updater): Update dependency argoproj-labs/argocd-image-updater to v1 (#3579)
* chore(argocd-image-updater): Update dependency argoproj-labs/argocd-image-updater to v1
Signed-off-by: argoproj-renovate[bot] <161757507+argoproj-renovate[bot]@users.noreply.github.com>
* chore: Sync more changes
Signed-off-by: Marco Maurer <[email protected]>
* chore: Update README
Signed-off-by: Marco Maurer <[email protected]>
* chore: Bump major chart version
Signed-off-by: Marco Maurer <[email protected]>
* chore: Sync NetworkPolicy for metrics
Signed-off-by: Marco Maurer <[email protected]>
* fix: Use containerPorts.metrics for metrics arg
Signed-off-by: Marco Maurer <[email protected]>
* chore: Sync suffix "-controller" to Deployment
Signed-off-by: Marco Maurer <[email protected]>
* chore: Also drop obsolete config key and refactor it to match Argo CD's approach
Signed-off-by: Marco Maurer <[email protected]>
* fix: ConfigMap can contain non-strings, quote them
Signed-off-by: Marco Maurer <[email protected]>
* fix: Use fullname in leader-election-role
Signed-off-by: Marco Maurer <[email protected]>
* ci: Do not keep CRDs between tests
Signed-off-by: Marco Maurer <[email protected]>
---------
Signed-off-by: argoproj-renovate[bot] <161757507+argoproj-renovate[bot]@users.noreply.github.com>
Signed-off-by: Marco Maurer <[email protected]>
Co-authored-by: argoproj-renovate[bot] <161757507+argoproj-renovate[bot]@users.noreply.github.com>
Co-authored-by: Marco Maurer <[email protected]>
Copy file name to clipboardExpand all lines: charts/argocd-image-updater/Chart.yaml
+4-4Lines changed: 4 additions & 4 deletions
Original file line number
Diff line number
Diff line change
@@ -2,8 +2,8 @@ apiVersion: v2
2
2
name: argocd-image-updater
3
3
description: A Helm chart for Argo CD Image Updater, a tool to automatically update the container images of Kubernetes workloads which are managed by Argo CD
If you still use the classic approach of installing Helm charts (non-OCI), you can do so by adding the Argo Helm repository and installing the chart with the following commands:
You will also need to run through the [secret setup documentation] so Argo CD Image Updater can talk to the Argo CD API (until its automated in this chart).
23
+
The Argo CD Image Updater controller **must** be run in the same Kubernetes cluster where your Argo CD `Application` resources are managed. The current controller architecture (v1.0+) does not support connecting to a remote Kubernetes cluster to manage applications.
18
24
19
25
## Prerequisites
20
26
21
27
* Helm v3.0.0+
22
28
23
-
## Configuration options
24
-
25
-
In order for your deployment of Argo CD Image Updater to be successful, you will need to make sure you set the correct configuration options described in detail on the [argocd-image-updater flags page].
29
+
## Changelog
26
30
27
-
All of the `argocd-` prefixed flags, which tell `argocd-image-updater` how your Argo CD instance is setup, are set in the `config.argocd` values block. For instance:
31
+
For full list of changes please check ArtifactHub [changelog].
28
32
29
-
```yaml
30
-
config:
31
-
argocd:
32
-
grpcWeb: false
33
-
serverAddress: "http://argocd.argo"
34
-
insecure: true
35
-
plaintext: true
36
-
```
37
-
38
-
Any additional arguments mentioned on the [argocd-image-updater flags page] can be configured using the `extraArgs` value, like so.
39
-
40
-
### Argo CD API key
33
+
Highlighted versions provide information about additional steps that should be performed by user when upgrading to newer version.
41
34
42
-
If you are unable to install Argo CD Image Updater into the same Kubernetes cluster you might configure it to use API of your Argo CD installation.
43
-
Please also read [Configuration of Container Registries].
44
-
45
-
```yaml
46
-
config:
47
-
argocd:
48
-
token: <your_secret_here>
49
-
```
35
+
### 1.0.0
50
36
51
-
If you specify a token value the secret will be created.
37
+
This chart release includes the upstream breaking changes introduced in Argo CD Image Updater 1.0.0.
38
+
Please read the migration docs carefully: https://argocd-image-updater.readthedocs.io/en/stable/configuration/migration/
52
39
53
40
### Registries
54
41
@@ -72,26 +59,25 @@ The `config.registries` value can be used exactly as it looks in the documentati
72
59
| authScripts.enabled | bool |`false`| Whether to mount the defined scripts that can be used to authenticate with a registry, the scripts will be mounted at `/scripts`|
73
60
| authScripts.name | string |`"argocd-image-updater-authscripts"`| Name of the authentication scripts ConfigMap |
74
61
| authScripts.scripts | object |`{}`| Map of key-value pairs where the key consists of the name of the script and the value the contents. |
75
-
| config.applicationsAPIKind | string | `""` | API kind that is used to manage Argo CD applications (`kubernetes` or `argocd`) |
76
-
| config.argocd.grpcWeb | bool | `true` | Use the gRPC-web protocol to connect to the Argo CD API |
77
-
| config.argocd.insecure | bool | `false` | If specified, the certificate of the Argo CD API server is not verified. |
78
-
| config.argocd.plaintext | bool | `false` | If specified, use an unencrypted HTTP connection to the Argo CD API instead of TLS. |
79
-
| config.argocd.serverAddress | string | `""` | Connect to the Argo CD API server at server address |
80
-
| config.argocd.token | string | `""` | If specified, the secret with Argo CD API key will be created. |
81
-
| config.argocd.tokenSecretName | string | `"argocd-image-updater-secret"` | Name of the Secret containing the token |
| config.name | string |`"argocd-image-updater-config"`| Name of the ConfigMap |
91
71
| config.registries | list |`[]`| Argo CD Image Updater registries list configuration. More information [here](https://argocd-image-updater.readthedocs.io/en/stable/configuration/registries/). |
| dualStack.ipFamilies | list |`[]`| IP families that should be supported and the order in which they should be applied to ClusterIP as well. Can be IPv4 and/or IPv6. |
97
83
| dualStack.ipFamilyPolicy | string |`""`| IP family policy to configure dual-stack see [Configure dual-stack](https://kubernetes.io/docs/concepts/services-networking/dual-stack/#services)|
@@ -118,7 +104,7 @@ The `config.registries` value can be used exactly as it looks in the documentati
118
104
| metrics.enabled | bool |`false`| Deploy metrics service |
119
105
| metrics.service.annotations | object |`{}`| Metrics service annotations |
120
106
| metrics.service.labels | object |`{}`| Metrics service labels |
121
-
| metrics.service.servicePort | int | `8081` | Metrics service port |
107
+
| metrics.service.servicePort | int |`8443`| Metrics service port |
If you still use the classic approach of installing Helm charts (non-OCI), you can do so by adding the Argo Helm repository and installing the chart with the following commands:
You will also need to run through the [secret setup documentation] so Argo CD Image Updater can talk to the Argo CD API (until its automated in this chart).
23
+
The Argo CD Image Updater controller **must** be run in the same Kubernetes cluster where your Argo CD `Application` resources are managed. The current controller architecture (v1.0+) does not support connecting to a remote Kubernetes cluster to manage applications.
18
24
19
25
## Prerequisites
20
26
21
27
* Helm v3.0.0+
22
28
23
-
## Configuration options
24
-
25
-
In order for your deployment of Argo CD Image Updater to be successful, you will need to make sure you set the correct configuration options described in detail on the [argocd-image-updater flags page].
29
+
## Changelog
26
30
27
-
All of the `argocd-` prefixed flags, which tell `argocd-image-updater` how your Argo CD instance is setup, are set in the `config.argocd` values block. For instance:
31
+
For full list of changes please check ArtifactHub [changelog].
28
32
29
-
```yaml
30
-
config:
31
-
argocd:
32
-
grpcWeb: false
33
-
serverAddress: "http://argocd.argo"
34
-
insecure: true
35
-
plaintext: true
36
-
```
37
-
38
-
Any additional arguments mentioned on the [argocd-image-updater flags page] can be configured using the `extraArgs` value, like so.
39
-
40
-
### Argo CD API key
33
+
Highlighted versions provide information about additional steps that should be performed by user when upgrading to newer version.
41
34
42
-
If you are unable to install Argo CD Image Updater into the same Kubernetes cluster you might configure it to use API of your Argo CD installation.
43
-
Please also read [Configuration of Container Registries].
44
-
45
-
```yaml
46
-
config:
47
-
argocd:
48
-
token: <your_secret_here>
49
-
```
35
+
### 1.0.0
50
36
51
-
If you specify a token value the secret will be created.
37
+
This chart release includes the upstream breaking changes introduced in Argo CD Image Updater 1.0.0.
38
+
Please read the migration docs carefully: https://argocd-image-updater.readthedocs.io/en/stable/configuration/migration/
52
39
53
40
### Registries
54
41
@@ -69,9 +56,5 @@ The `config.registries` value can be used exactly as it looks in the documentati
69
56
----------------------------------------------
70
57
Autogenerated from chart metadata using [helm-docs](https://github.com/norwoodj/helm-docs)
0 commit comments