|
| 1 | +// Module included in the following assembly: |
| 2 | +// |
| 3 | +// * release_notes/gitops-release-notes-1-16.adoc |
| 4 | + |
| 5 | +:_mod-docs-content-type: REFERENCE |
| 6 | + |
| 7 | +[id="gitops-release-notes-1-16-2_{context}"] |
| 8 | += Release notes for {gitops-title} 1.16.2 |
| 9 | + |
| 10 | +{gitops-title} 1.16.2 is now available on {OCP} 4.12, 4.14, 4.15, 4.16, 4.17, and 4.18. |
| 11 | + |
| 12 | +[id="errata-updates-1-16.2_{context}"] |
| 13 | +== Errata updates |
| 14 | + |
| 15 | +[id="RHSA-2025:9506-gitops-1-16-2-security-update-advisory_{context}"] |
| 16 | +=== RHSA-2025:9506 - {gitops-title} 1.16.2 security update advisory |
| 17 | + |
| 18 | +Issued: 2025-06-24 |
| 19 | + |
| 20 | +The list of security fixes that are included in this release is documented in the following advisory: |
| 21 | + |
| 22 | +* link:https://access.redhat.com/errata/RHSA-2025:9506[RHSA-2025:9506] |
| 23 | + |
| 24 | +If you have installed the {gitops-title} Operator in the default namespace, run the following command to view the container images in this release: |
| 25 | + |
| 26 | +[source,terminal] |
| 27 | +---- |
| 28 | +$ oc describe deployment gitops-operator-controller-manager -n openshift-gitops-operator |
| 29 | +---- |
| 30 | + |
| 31 | +[id="fixed-issues-1-16-2_{context}"] |
| 32 | +== Fixed issues |
| 33 | + |
| 34 | +* Before this update, Argo CD monitoring worked automatically when deployed in any namespace and user-workload monitoring support for workloads did not require any manual configuration. With this update, if you deploy Argo CD in a non-{OCP} namespace, you must enable user-workload monitoring in {OCP}. For more information, see link:https://docs.redhat.com/en/documentation/openshift_container_platform/latest/html/monitoring/configuring-user-workload-monitoring#enabling-monitoring-for-user-defined-projects-uwm_preparing-to-configure-the-monitoring-stack-uwm[Enabling monitoring for user-defined projects]. link:https://issues.redhat.com/browse/GITOPS-7037[GITOPS-7037] |
| 35 | + |
| 36 | +* Before this update, the {gitops-title} Operator did not correctly handle regular expressions in `sourceNamespaces`, leading to an unexpected behavior when matching namespace patterns. With this update, the {gitops-title} Operator now uses the correct regex option, `glob.REGEXP`, instead of `glob.GLOB` when processing `getSourceNamespaces`, ensuring that regular expressions are evaluated and matched accurately. link:https://issues.redhat.com/browse/GITOPS-6675[GITOPS-6675] |
| 37 | + |
| 38 | +* Before this update, the `gitops-plugin` deployment created by the {gitops-title} Operator did not include a security context, causing the plugin pod to fail in environments that enforce the `PodSecurity` restricted policy. With this update, the {gitops-title} Operator now sets the required security context for the `gitops-plugin` deployment, ensuring compliance with the `PodSecurity` restricted policy. link:https://issues.redhat.com/browse/GITOPS-6777[GITOPS-6777] |
0 commit comments