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
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:
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.
24
24
25
+
### Choosing the installation namespace
26
+
27
+
> You have two options for where to install the Argo CD Image Updater:
28
+
>
29
+
> #### Option 1: Install into the Argo CD namespace (Recommended)
30
+
>
31
+
> The simplest approach is to install the image updater into the same namespace as your Argo CD installation. This
32
+
> requires minimal configuration. (..)
33
+
>
34
+
> #### Option 2: Install into a separate namespace
35
+
>
36
+
> For better workload isolation, you can install the image updater into its own namespace. This use case requires
37
+
> several manual configuration steps. (..)
38
+
39
+
For the full details, please read [Installation methods] in the upstream docs.
40
+
25
41
## Prerequisites
26
42
27
43
* Helm v3.0.0+
@@ -32,6 +48,13 @@ For full list of changes please check ArtifactHub [changelog].
32
48
33
49
Highlighted versions provide information about additional steps that should be performed by user when upgrading to newer version.
34
50
51
+
### 1.0.3 (app version 1.0.2)
52
+
53
+
The upstream project changed the recommended installation namespace from `argocd-image-updater-system` to the same
54
+
namespace as Argo CD is installed in.
55
+
56
+
Please read [Installation methods] and/or [PR #1356] for more information.
57
+
35
58
### 1.0.0
36
59
37
60
This chart release includes the upstream breaking changes introduced in Argo CD Image Updater 1.0.0.
@@ -124,6 +147,7 @@ The `config.registries` value can be used exactly as it looks in the documentati
124
147
| resources | object |`{}`| Pod memory and cpu resource settings for the deployment |
125
148
| securityContext | object | See [values.yaml]| Security context settings for the deployment |
126
149
| service.annotations | object |`{}`| Service annotations |
150
+
| service.enabled | bool |`false`| Enable a Service for the webhook endpoint. A Service is created when this is set to true or when `ingress.enabled` is true |
127
151
| service.externalIPs | list |`[]`| Service external IPs |
128
152
| service.externalTrafficPolicy | string |`"Cluster"`| Denotes if this Service desires to route external traffic to node-local or cluster-wide endpoints |
129
153
| service.labels | object |`{}`| Service labels |
@@ -150,3 +174,5 @@ Autogenerated from chart metadata using [helm-docs](https://github.com/norwoodj/
150
174
151
175
[Configuration of Container Registries]: https://argocd-image-updater.readthedocs.io/en/stable/configuration/registries/
0 commit comments