|
| 1 | +// Module included in the following assembly: |
| 2 | +// |
| 3 | +// * gitops/gitops-release-notes.adoc |
| 4 | +:_content-type: REFERENCE |
| 5 | + |
| 6 | +[id="gitops-release-notes-1-7-0_{context}"] |
| 7 | += Release notes for {gitops-title} 1.7.0 |
| 8 | + |
| 9 | +{gitops-title} 1.7.0 is now available on {product-title} 4.8, 4.9, 4.10, and 4.11. |
| 10 | + |
| 11 | +[id="new-features-1-7-0_{context}"] |
| 12 | +== New features |
| 13 | + |
| 14 | +The current release adds the following improvements: |
| 15 | + |
| 16 | +* With this update, you can add environment variables to the Notifications controller. link:https://issues.redhat.com/browse/GITOPS-2313[GITOPS-2313] |
| 17 | + |
| 18 | +* With this update, the default nodeSelector `"kubernetes.io/os": "linux"` key-value pair is added to all workloads such that they only schedule on Linux nodes. In addition, any custom node selectors are added to the default and take precedence if they have the same key. link:https://issues.redhat.com/browse/GITOPS-2215[GITOPS-2215] |
| 19 | + |
| 20 | +* With this update, you can set custom node selectors in the Operator workloads by editing their `GitopsService` custom resource. link:https://issues.redhat.com/browse/GITOPS-2164[GITOPS-2164] |
| 21 | + |
| 22 | +* With this update, you can use the RBAC policy matcher mode to select from the following options: `glob` (default) and `regex`.link:https://issues.redhat.com/browse/GITOPS-1975[GITOPS-1975] |
| 23 | + |
| 24 | +* With this update, you can customize resource behavior using the following additional subkeys: |
| 25 | ++ |
| 26 | +[options=header] |
| 27 | +|=== |
| 28 | +| Subkey | Key form | Mapped field in argocd-cm |
| 29 | +| resourceHealthChecks | resource.customizations.health.<group_kind> | resource.customizations.health |
| 30 | +| resourceIgnoreDifferences | resource.customizations.ignoreDifferences.<group_kind> | resource.customizations.ignoreDifferences |
| 31 | +| resourceActions | resource.customizations.actions.<group_kind> | resource.customizations.actions |
| 32 | +|=== |
| 33 | ++ |
| 34 | +link:https://issues.redhat.com/browse/GITOPS-1561[GITOPS-1561] |
| 35 | ++ |
| 36 | +[NOTE] |
| 37 | +==== |
| 38 | +In future releases, there is a possibility to deprecate the old method of customizing resource behavior by using only resourceCustomization and not subkeys. |
| 39 | +==== |
| 40 | + |
| 41 | +* With this update, to use the *Environments* feature on the *Developer* tab you must upgrade if you are using a {gitops-title} version prior to 1.7 and {product-title} 4.15 or above. link:https://issues.redhat.com/browse/GITOPS-2415[GITOPS-2415] |
| 42 | + |
| 43 | +* With this update, applications can be created in any namespace in the same cluster and still managed by the same control-plane’s ArgoCD instance. This is done by adding a new label `argocd.argoproj.io/managed-by-cluster-argocd` to the namespace added in `spec.sourceNamespaces` of the Argo CD custom resource. link:https://issues.redhat.com/browse/GITOPS-2341[GITOPS-2341] |
| 44 | ++ |
| 45 | +:FeatureName: Argo CD Applications controller |
| 46 | +include::snippets/technology-preview.adoc[] |
| 47 | + |
| 48 | +[id="fixed-issues-1-7-0_{context}"] |
| 49 | +== Fixed issues |
| 50 | + |
| 51 | +The following issues have been resolved in the current release: |
| 52 | + |
| 53 | +* Before this update, {gitops-title} releases were affected by an issue of Dex pods failing with `CreateContainerConfigError` error when the `anyuid` SCC was assigned to the Dex service account. This update fixes the issue by assigning a default user id to the Dex container. link:https://issues.redhat.com/browse/GITOPS-2235[GITOPS-2235] |
| 54 | + |
| 55 | +* Before this update, {gitops-title} used the RHSSO (Keycloak) through OIDC in addition to Dex. However, with a recent security fix, the certificate of RHSSO could not be validated when configured with a certificate not signed by one of the well-known certificate authorities. This update fixes the issue; you can now provide a custom certificate to verify the KeyCloak's TLS certificate while communicating with it. In addition, you can add `rootCA` to the Argo CD custom resource `.spec.keycloak.rootCA` field. The Operator reconciles such changes and updates the `oidc.config in argocd-cm` config map with the PEM encoded root certificate. link:https://issues.redhat.com/browse/GITOPS-2214[GITOPS-2214] |
| 56 | + |
| 57 | +Example Argo CD with Keycloak configuration: |
| 58 | + |
| 59 | +[source,yaml] |
| 60 | +---- |
| 61 | +apiVersion: argoproj.io/v1alpha1 |
| 62 | +kind: ArgoCD |
| 63 | +metadata: |
| 64 | + name: example-argocd |
| 65 | +spec: |
| 66 | + sso: |
| 67 | + keycloak: |
| 68 | + rootCA: '<PEM encoded root certificate>' |
| 69 | + provider: keycloak |
| 70 | +....... |
| 71 | +....... |
| 72 | +---- |
| 73 | + |
| 74 | +* Before this update, the application controllers restarted multiple times due to the unresponsiveness of liveness probes. This update fixes the issue by removing the liveness probe in the `statefulset` application controller. link:https://issues.redhat.com/browse/GITOPS-2153[GITOPS-2153] |
| 75 | + |
| 76 | +[id="known-issues-1-7-0_{context}"] |
| 77 | +== Known issues |
| 78 | + |
| 79 | +* Before this update, the Operator did not reconcile the `mountsatoken` and `ServiceAccount` settings for the repository server. While this has been fixed, deletion of the service account does not revert to the default. link:https://issues.redhat.com/browse/GITOPS-1873[GITOPS-1873] |
| 80 | + |
| 81 | +* Workaround: Manually set the `spec.repo.serviceaccountfield to thedefault` service account. link:https://issues.redhat.com/browse/GITOPS-2452[GITOPS-2452] |
0 commit comments