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: modules/gitops-release-notes-1-4-0.adoc
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -12,7 +12,7 @@
12
12
13
13
The current release adds the following improvements.
14
14
15
-
* This enhancement upgrades {gitops-title} Application Manager (kam) to version *0.0.41*. link:https://issues.redhat.com/browse/GITOPS-1669[GITOPS-1669]
15
+
* This enhancement upgrades the {gitops-title} Application Manager CLI (`kam`) to version *0.0.41*. link:https://issues.redhat.com/browse/GITOPS-1669[GITOPS-1669]
16
16
17
17
* This enhancement upgrades Argo CD to version *2.2.2*. link:https://issues.redhat.com/browse/GITOPS-1532[GITOPS-1532]
18
18
@@ -33,7 +33,7 @@ With this update, administrators can configure a common cluster role for all the
33
33
34
34
The following issues have been resolved in the current release:
35
35
36
-
* Before this update, when the Route to the {gitops-title} Application Manager (kam) was accessed without specifying a path in the URL, a default page without any helpful information was displayed to the user. This update fixes the issue so that the default page displays download links for kam. link:https://issues.redhat.com/browse/GITOPS-923[GITOPS-923]
36
+
* Before this update, when the Route to the {gitops-title} Application Manager CLI (`kam`) was accessed without specifying a path in the URL, a default page without any helpful information was displayed to the user. This update fixes the issue so that the default page displays download links for the `kam` CLI. link:https://issues.redhat.com/browse/GITOPS-923[GITOPS-923]
37
37
38
38
* Before this update, setting a resource quota in the namespace of the Argo CD custom resource might cause the setup of the Red Hat SSO (RH SSO) instance to fail. This update fixes this issue by setting a minimum resource request for the RH SSO deployment pods. link:https://issues.redhat.com/browse/GITOPS-1297[GITOPS-1297]
{gitops-title} 1.8.0 is now available on {product-title} 4.10, 4.11, and 4.12.
10
+
11
+
[id="errata-updates-1-8-0_{context}"]
12
+
== New features
13
+
14
+
The current release adds the following improvements:
15
+
16
+
* With this update, you can add support for the ApplicationSet Progressive Rollout Strategy feature. Using this feature, you can enhance the ArgoCD ApplicationSet resource to embed a rollout strategy for a progressive application resource update after you modify the ApplicationSet spec or Application templates. When you enable this feature, applications are updated in a declarative order instead of simultaneously. link:https://issues.redhat.com/browse/GITOPS-956[GITOPS-956]
17
+
+
18
+
[IMPORTANT]
19
+
====
20
+
ApplicationSet Progressive Rollout Strategy is a Technology Preview feature.
21
+
====
22
+
//https://github.com/argoproj/argo-cd/pull/12103
23
+
24
+
* With this update, the *Application environments* page in the *Developer* perspective of the {product-title} web console is decoupled from the {gitops-title} Application Manager command-line interface (CLI), `kam`. You do not have to use the `kam` CLI to generate Application Environment manifests for the environments to show up in the *Developer* perspective of the {product-title} web console. You can use your own manifests, but the environments must still be represented by namespaces. In addition, specific labels and annotations are still needed. link:https://issues.redhat.com/browse/GITOPS-1785[GITOPS-1785]
25
+
26
+
* With this update, the {gitops-title} Operator and the `kam` CLI are now available to use on ARM architecture on {product-title}. link:https://issues.redhat.com/browse/GITOPS-1688[GITOPS-1688]
27
+
+
28
+
[IMPORTANT]
29
+
====
30
+
`spec.sso.provider: keycloak` is not yet supported on ARM.
31
+
====
32
+
33
+
* With this update, you can enable workload monitoring for specific Argo CD instances by setting the `.spec.monitoring.enabled` flag value to `true`. As a result, the Operator creates a `PrometheusRule` object that contains alert rules for each Argo CD component. These alert rules trigger an alert when the replica count of the corresponding component has drifted from the desired state for a certain amount of time. The Operator will not overwrite the changes made to the `PrometheusRule` object by the users. link:https://issues.redhat.com/browse/GITOPS-2459[GITOPS-2459]
34
+
35
+
* With this update, you can pass command arguments to the repo server deployment using the Argo CD CR. link:https://issues.redhat.com/browse/GITOPS-2445[GITOPS-2445]
36
+
+
37
+
For example:
38
+
+
39
+
[source,yaml]
40
+
----
41
+
apiVersion: argoproj.io/v1alpha1
42
+
kind: ArgoCD
43
+
metadata:
44
+
name: example-argocd
45
+
spec:
46
+
repo:
47
+
extraRepoCommandArgs:
48
+
- --max.combined.directory.manifests.size
49
+
- 10M
50
+
----
51
+
52
+
[id="fixed-issues-1-8-0_{context}"]
53
+
== Fixed issues
54
+
55
+
The following issues have been resolved in the current release:
56
+
57
+
* Before this update, you could set the `ARGOCD_GIT_MODULES_ENABLED` environment variable only on the `openshift-gitops-repo-server` pod and not on the `ApplicationSet Controller` pod. As a result, when using the Git generator, Git submodules were cloned during the generation of child applications because the variable was missing from the `ApplicationSet Controller` environment. In addition, if the credentials required to clone these submodules were not configured in ArgoCD, the application generation failed. This update fixes the issue; you can now add any environment variables such as `ArgoCD_GIT_MODULES_ENABLED` to the `ApplicationSet Controller` pod using the Argo CD CR. The `ApplicationSet Controller` pod then successfully generates child applications from the cloned repository and no submodule is cloned in the process. link:https://issues.redhat.com/browse/GITOPS-2399[GITOPS-2399]
58
+
+
59
+
For example:
60
+
+
61
+
[source,yaml]
62
+
----
63
+
apiVersion: argoproj.io/v1alpha1
64
+
kind: ArgoCD
65
+
metadata:
66
+
name: example-argocd
67
+
labels:
68
+
example: basic
69
+
spec:
70
+
applicationSet:
71
+
env:
72
+
- name: ARGOCD_GIT_MODULES_ENABLED
73
+
value: "true"
74
+
----
75
+
76
+
* Before this update, while installing the {gitops-title} Operator v1.7.0, the default `argocd-cm.yml` config map file created for authenticating Dex contained the base64-encoded client secret in the format of a `key:value` pair. This update fixes this issue by not storing the client secret in the default `argocd-cm.yml` config map file. Instead, the client secret is inside an `argocd-secret` object now, and you can reference it inside the configuration map as a secret name. link:https://issues.redhat.com/browse/GITOPS-2570[GITOPS-2570]
77
+
78
+
[id="known-issues-1-8-0_{context}"]
79
+
== Known issues
80
+
81
+
* When you deploy applications using your manifests without using the `kam` CLI and view the applications in the *Application environments* page in the *Developer* perspective of the {product-title} web console, the Argo CD URL to the corresponding application does not load the page as expected from the Argo CD icon in the card. link:https://issues.redhat.com/browse/GITOPS-2736[GITOPS-2736]
0 commit comments