RHDEVDOCS-7020: Content creation for GitOps 1.18.2 RN

modules/gitops-release-notes-1-18-2.adoc

@@ -0,0 +1,59 @@
+// Module included in the following assembly:
+//
+// * release_notes/gitops-release-notes-1-18.adoc
+
+:_mod-docs-content-type: REFERENCE
+
+[id="gitops-release-notes-1-18-2_{context}"]
+= Release notes for {gitops-title} 1.18.2
+
+{gitops-title} 1.18.2 is available on {OCP} 4.14, 4.16, 4.17, 4.18, and 4.19.
+
+[id="errata-updates-1-18-2_{context}"]
+== Errata updates
+
+[id="RHSA-XXXX:NNNN-gitops-1-18-2-security-update-advisory_{context}"]
+=== RHSA-XXXX:NNNN - {gitops-title} 1.18.2 security update advisory
+
+Issued: 2025-12-10
+
+The list of security fixes included in this release is available in the following advisory:
+
+* link:https://access.redhat.com/errata/RHSA-XXXX:NNNN[RHSA-XXXX:NNNN]
+
+If you have installed the {gitops-title} Operator in the default namespace, run the following command to view the container images in this release:
+
+[source,terminal]
+----
+$ oc describe deployment gitops-operator-controller-manager -n openshift-gitops-operator
+----
+
+[id="new-features-1-18-2_{context}"]
+== New features
+
+* With this update, the Redis version included with {gitops-title} is upgraded to `v7.2.11`.
++
+link:https://issues.redhat.com/browse/GITOPS-8019[GITOPS-8019]
+
+[id="fixed-issues-1-18-2_{context}"]
+== Fixed issues
+
+GitOps Operator pulls images from registry.redhat.io::
+Before this update, when the `.spec.version` field was set in the Argo CD CR, the {gitops-title} Operator incorrectly pulled upstream images from `quay.io`. With this update, this issue is fixed. The {gitops-title} Operator pulls images from `registry.redhat.io` and only uses certified images from the Red Hat registry.
++
+link:https://issues.redhat.com/browse/GITOPS-7789[GITOPS-7789]
+
+Revised rolling update strategy for HAProxy deployment::
+Before this update, the `openshift-gitops-redis-ha-haproxy` deployment failed to upgrade on a three-worker node cluster due to a combination of pod anti-affinity rules and the update strategy. With this update, the {gitops-title} Operator revises the rolling update strategy to fix this issue.
++
+link:https://issues.redhat.com/browse/GITOPS-8033[GITOPS-8033]
+
+Added ingress permissions for successful reconciliation::
+Before this update, the {gitops-title} Operator failed to reconcile when `spec.applicationSet.webhookServer.route.enabled` was set to `true` in the Argo CD CR. This issue occurred because the {gitops-title} Operator lacked the required ingress permissions for `config.openshift.io`. With this update, the {gitops-title} Operator includes the necessary permissions and reconciles successfully.
++
+link:https://issues.redhat.com/browse/GITOPS-8152[GITOPS-8152]
+
+Improved Redis HA startup reliability::
+Before this update, in the Redis high availability (HA) mode, the Redis config `init` container could hang for several minutes while detecting the master container, causing Redis pods to take a long time to become _Ready_. With this update, the master container detection logic includes a connection timeout, which prevents the `init` container from blocking and ensures a faster, more reliable Redis HA startup.
++
+link:https://issues.redhat.com/browse/GITOPS-7608[GITOPS-7608]

release_notes/gitops-release-notes-1-18.adoc

@@ -29,6 +29,9 @@ include::modules/go-compatibility-and-support-matrix.adoc[leveloffset=+1]
 
 // Modules included, most to least recent
 
+// Release notes for Red Hat OpenShift GitOps 1.18.2
+include::modules/gitops-release-notes-1-18-2.adoc[leveloffset=+1]
+
 // Release notes for Red Hat OpenShift GitOps 1.18.1
 include::modules/gitops-release-notes-1-18-1.adoc[leveloffset=+1]