|
| 1 | +// Module included in the following assembly: |
| 2 | +// |
| 3 | +// * gitops/gitops-release-notes.adoc |
| 4 | + |
| 5 | +[id="gitops-release-notes-1-2-1_{context}"] |
| 6 | += Release notes for {gitops-title} 1.2.1 |
| 7 | + |
| 8 | +{gitops-title} 1.2.1 is now available on {product-title} 4.7 and 4.8. |
| 9 | + |
| 10 | +[id="support-matrix-1-2-1_{context}"] |
| 11 | +== Support matrix |
| 12 | + |
| 13 | +Some features in this release are currently in Technology Preview. These experimental features are not intended for production use. |
| 14 | + |
| 15 | +link:https://access.redhat.com/support/offerings/techpreview[Technology Preview Features Support Scope] |
| 16 | + |
| 17 | +In the table below, features are marked with the following statuses: |
| 18 | + |
| 19 | +- *TP*: _Technology Preview_ |
| 20 | + |
| 21 | +- *GA*: _General Availability_ |
| 22 | + |
| 23 | +Note the following scope of support on the Red Hat Customer Portal for these features: |
| 24 | + |
| 25 | +.Support matrix |
| 26 | +[cols="1,1",options="header"] |
| 27 | +|=== |
| 28 | +| Feature | {gitops-title} 1.2.1 |
| 29 | +| Argo CD |
| 30 | +| GA |
| 31 | +| Argo CD ApplicationSet |
| 32 | +| TP |
| 33 | +| {gitops-title} Application Manager (kam) |
| 34 | +| TP |
| 35 | +| {gitops-title} Service |
| 36 | +| TP |
| 37 | +|=== |
| 38 | + |
| 39 | +[id="fixed-issues-1-2-1_{context}"] |
| 40 | +== Fixed issues |
| 41 | +The following issues were resolved in the current release: |
| 42 | + |
| 43 | +* Previously, huge memory spikes were observed on the application controller on startup. The flag `--kubectl-parallelism-limit` for the application controller is now set to 10 by default, however |
| 44 | +this value can be overridden by specifying a number for `.spec.controller.kubeParallelismLimit` in the Argo CD CR specification. |
| 45 | +link:https://issues.redhat.com/browse/GITOPS-1255[GITOPS-1255] |
| 46 | + |
| 47 | +* The latest Triggers APIs caused Kubernetes build failure due to duplicate entries in the kustomization.yaml when using the `kam bootstrap` command. The Pipelines and Tekton triggers components have now been updated to v0.24.2 and v0.14.2, respectively, to address this issue. |
| 48 | +link:https://issues.redhat.com/browse/GITOPS-1273[GITOPS-1273] |
| 49 | + |
| 50 | +* Persisting RBAC roles and bindings are now automatically removed from the target namespace when the Argo CD instance from the source namespace is deleted. |
| 51 | +link:https://issues.redhat.com/browse/GITOPS-1228[GITOPS-1228] |
| 52 | + |
| 53 | +* Previously, when deploying an Argo CD instance into a namespace, the Argo CD instance would change the "managed-by" label to be its own namespace. This fix would make namespaces unlabelled while also making sure the required RBAC roles and bindings are created and deleted for the namespace. |
| 54 | +link:https://issues.redhat.com/browse/GITOPS-1247[GITOPS-1247] |
| 55 | + |
| 56 | +* Previously, the default resource request limits on Argo CD workloads, specifically for the repo-server and application controller, were found to be very restrictive. The existing resource quota has now been removed and the default memory limit has been increased to 1024M in the repo server. Please note that this change will only affect new installations; existing Argo CD instance workloads will not be affected. |
| 57 | +link:https://issues.redhat.com/browse/GITOPS-1274[GITOPS-1274] |
0 commit comments