diff --git a/modules/gitops-creating-aggregated-cluster-roles.adoc b/modules/gitops-creating-aggregated-cluster-roles.adoc index 267c4de19b71..938453e81f8d 100644 --- a/modules/gitops-creating-aggregated-cluster-roles.adoc +++ b/modules/gitops-creating-aggregated-cluster-roles.adoc @@ -14,7 +14,7 @@ The process of creating aggregated cluster roles consists of the following proce [id="enable-creation-of-aggregated-cluster-roles_{context}"] == Enable the creation of aggregated cluster roles -You can enable the creation of aggregated cluster roles by setting the value of the `.spec.aggregatedClusterRoles` field to `true` in the Argo CD custom resource (CR). When you enable the creation of aggregated cluster roles, the {gitops} Operator takes the following actions: +You can enable the creation of aggregated cluster roles by setting the value of the `.spec.aggregatedClusterRoles` field to `true` in the Argo CD custom resource (CR). When you enable the creation of aggregated cluster roles, the {gitops-title} Operator takes the following actions: * Creates an `--argocd-application-controller` aggregated cluster role with a predefined `aggregationRule` field by default. * Creates a corresponding cluster role binding and manages it. diff --git a/modules/gitops-release-notes-1-16-0.adoc b/modules/gitops-release-notes-1-16-0.adoc index 0e088e7311ac..f72603819331 100644 --- a/modules/gitops-release-notes-1-16-0.adoc +++ b/modules/gitops-release-notes-1-16-0.adoc @@ -96,6 +96,14 @@ With this update, this issue is fixed. This update resolves the issue by integra [id="known-issues-1-16-0_{context}"] == Known Issues -* There is currently a known issue that assigns a lower `SecurityContextConstraints` (SCC) to Redis service account in {gitops-shortname} v1.16 after upgrading from {gitops-shortname} v1.15 to v1.16. The {gitops-shortname} Operator does not update the `securityContext` of the `redis-ha-server` StatefulSet, which causes the container's user to be statically set instead of being randomly assigned as required by the `restricted-v2` SCC. The `redis-ha-server` StatefulSet pods retain the old configurations and are not updated with the new settings. As a result, the new configuration of the StatefulSet is not applied correctly. +* There is currently a known issue that assigns a lower `SecurityContextConstraints` (SCC) to Redis service account in {gitops-shortname} v1.16 after upgrading from {gitops-shortname} v1.15 to v1.16. The {gitops-shortname} Operator does not update the `securityContext` of the `redis-ha-server` `StatefulSet`, which causes the container's user to be statically set instead of being randomly assigned as required by the `restricted-v2` SCC. The `redis-ha-server` `StatefulSet` pods retain the old configurations and are not updated with the new settings. As a result, the new configuration of the `StatefulSet` is not applied correctly. + -Workaround: Manually delete the `redis-ha-server` StatefulSet to trigger the re-creation of the pods with the updated settings. link:https://issues.redhat.com/browse/GITOPS-6670[GITOPS-6670] \ No newline at end of file +Workaround: Manually delete the `redis-ha-server` `StatefulSet` to trigger the re-creation of the pods with the updated settings. link:https://issues.redhat.com/browse/GITOPS-6670[GITOPS-6670] + +[id="deprecated-features-1-16-0_{context}"] +== Deprecated and removed features + +[id="deprecation-of-some-fields-in-argo-cd_{context}"] +=== Deprecation of `.spec.initialRepositories` & `.spec.repositoryCredentials` fields in Argo CD + +* In {gitops-title} v1.16, the `.spec.initialRepositories` and `.spec.repositoryCredentials` fields in Argo CD CR are deprecated. These fields will no longer be supported by {gitops-title} Operator and the Argo CD CR in a future release. Update your configurations to remove dependencies on these fields. Use the Argo CD web UI or CLI to add or modify repositories. link:https://issues.redhat.com/browse/GITOPS-5961[GITOPS-5961] \ No newline at end of file diff --git a/understanding_openshift_gitops/about-redhat-openshift-gitops.adoc b/understanding_openshift_gitops/about-redhat-openshift-gitops.adoc index d53d5216b8c7..f86806a1a43e 100644 --- a/understanding_openshift_gitops/about-redhat-openshift-gitops.adoc +++ b/understanding_openshift_gitops/about-redhat-openshift-gitops.adoc @@ -12,9 +12,9 @@ toc::[] ==== Because {gitops-title} releases on a different cadence from {OCP}, the {gitops-title} documentation is now available as separate documentation sets for each minor version of the product. -The {gitops-title} documentation is available at link:https://docs.openshift.com/gitops/[]. +The {gitops-title} documentation is available at link:https://docs.redhat.com/en/documentation/red_hat_openshift_gitops/[]. -Documentation for specific versions is available using the version selector dropdown, or directly by adding the version to the URL, for example, link:https://docs.openshift.com/gitops/1.8[]. +Documentation for specific versions is available using the version selector dropdown, or directly by adding the version to the URL, for example, link:https://docs.redhat.com/en/documentation/red_hat_openshift_gitops/1.16[]. In addition, the {gitops-title} documentation is also available on the Red Hat Portal at https://access.redhat.com/documentation/en-us/red_hat_openshift_gitops/[].