Skip to content

Commit 565048b

Browse files
authored
Merge pull request #58017 from Srivaralakshmi/GitOpsRN-1-8-2
Document GitOps 1.8.2 Release Notes
2 parents 91abf73 + 29f77fd commit 565048b

File tree

2 files changed

+24
-0
lines changed

2 files changed

+24
-0
lines changed

cicd/gitops/gitops-release-notes.adoc

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -23,6 +23,8 @@ include::modules/go-compatibility-and-support-matrix.adoc[leveloffset=+1]
2323
include::modules/making-open-source-more-inclusive.adoc[leveloffset=+1]
2424

2525
// Modules included, most to least recent
26+
include::modules/gitops-release-notes-1-8-2.adoc[leveloffset=+1]
27+
2628
include::modules/gitops-release-notes-1-8-1.adoc[leveloffset=+1]
2729

2830
include::modules/gitops-release-notes-1-8-0.adoc[leveloffset=+1]
Lines changed: 22 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,22 @@
1+
// Module included in the following assembly:
2+
//
3+
// * gitops/gitops-release-notes.adoc
4+
:_content-type: REFERENCE
5+
[id="gitops-release-notes-1-8-2_{context}"]
6+
= Release notes for {gitops-title} 1.8.2
7+
8+
{gitops-title} 1.8.2 is now available on {product-title} 4.10, 4.11, and 4.12.
9+
10+
[id="fixed-issues-1-8-2_{context}"]
11+
== Fixed issues
12+
13+
The following issues have been resolved in the current release:
14+
15+
* Before this update, when you configured Dex using the `.spec.dex` parameter and tried to log in to the Argo CD UI by using the *LOG IN VIA OPENSHIFT* option, you were not able to log in. This update fixes the issue.
16+
+
17+
[IMPORTANT]
18+
====
19+
The `spec.dex` parameter in the ArgoCD CR is deprecated. In a future release of {gitops-title} v1.9, configuring Dex using the `spec.dex` parameter in the ArgoCD CR is planned to be removed. Consider using the `.spec.sso` parameter instead. See "Enabling or disabling Dex using .spec.sso". link:https://issues.redhat.com/browse/GITOPS-2761[GITOPS-2761]
20+
====
21+
22+
* Before this update, the cluster and `kam` CLI pods failed to start with a new installation of {gitops-title} v1.8.0 on the {product-title} 4.10 cluster. This update fixes the issue and now all pods run as expected. link:https://issues.redhat.com/browse/GITOPS-2762[GITOPS-2762]

0 commit comments

Comments
 (0)