Chapter 1. Red Hat OpenShift GitOps release notes

Before this update, when using the dynamic scaling feature, application controller pods consumed high memory and clusters were not distributed properly across shards. This update ensures that clusters are distributed across shards. GITOPS-5811

For more information, see Enabling dynamic scaling of shards in the web console section

With this update, you can configure Argo CD to disable the automatic scraping of metrics for your instance. Before this update, there was no option to disable this feature, resulting in excessive storage usage when multiple Argo CD instances were available on the cluster. GITOPS-4519

To disable metrics for your Argo CD instance, edit the spec.monitoring.disableMetrics field in the Argo CD CR to true.

apiVersion: argoproj.io/v1beta1
kind: ArgoCD
metadata:
 name: argocd-sample
 namespace: default
spec:
 monitoring:
   disableMetrics: true

Use the following command to scrape metrics in the Argo CD CLI:

$ oc patch argocd argocd-sample -n default --type='json' -p='[{"op": "replace", "path": "/spec/monitoring/disableMetrics", "value": true}]'

With this update, the Argo Rollouts functionality in Red Hat OpenShift GitOps is promoted from Technology Preview (TP) to General Availability (GA). GITOPS-3848

Use this feature to perform the following actions:

With this update, the following new commands are introduced for the Argo CD applications in non-control plane namespaces feature:

With this update, Argo CD CLI has been enhanced by enabling the --app-namespace flag for various application-related commands. GITOPS-3834

This flag allows users to specify the namespace for operations such as waiting, rolling back, patching, editing, diffing, viewing history, syncing, and deleting applications. As a result, the following commands are updated in Red Hat OpenShift GitOps:

There is currently a known issue that prevents the Red Hat OpenShift GitOps Operator from updating the default TLS termination policy of the Argo CD server route from Passthrough to Reencrypt. This is a race condition that occurs when upgrading from an older version. GITOPS-4947

Workaround: Delete the Argo CD server route and the Argo CD server pod. The recreated route and pod now uses the Reencrypt policy.

With this update, support has been provided for the must-gather tool in the Argo Rollouts controller. This update provides support for the following enhancements:

Before this update, users were unable to include context for notifications in the NotificationsConfiguration custom resource (CR). With this update, users can now add context for notifications by using the context field in the NotificationsConfiguration CR. This field can also be used to establish shared context across all templates defined in the NotificationsConfiguration CR. GITOPS-4303

spec:
  context:
    region: east 1

With this update, the GitOps argocd CLI is supported and accessible as a productized component of Red Hat OpenShift GitOps. The GitOps argocd CLI tool is available through RPMs in RHEL. You can download it through the OpenShift mirror registry.

By using the GitOps argocd CLI tool, you can complete the following tasks:

With this update, NotificationsConfiguration custom resource (CR) is now supported. Before this update, you had to update the argocd-notifications-cm ConfigMap to manage templates, triggers, services and subscriptions. With this release, you cannot modify the argocd-notifications-cm ConfigMap. A new Custom Resource definition NotificationsConfiguration is introduced to manage the argocd-notifications-cm ConfigMap. GITOPS-4130

With this update, two new fields .spec.applicationSet.sourceNamespaces and .spec.applicationSet.scmProviders are introduced in the ArgoCD CRD to support ApplicationSet in any non-control plane namespaces. Administrators can use these fields to define certain namespaces that manage ApplicationSet resources. GITOPS-3754

With this update, you can configure log levels, such as debug, info, warn, error, panic and fatal. The default log level set for the output is info. To change the log level, add the environment variable LOG_LEVEL in the .spec.config.env field of the Subscription CR. GITOPS-4016

apiVersion: operators.coreos.com/v1alpha1
kind: Subscription
metadata:
  name: gitops-operator
  namespace: openshift-gitops-operator
spec:
  ...
  config:
    env:
    - name: LOG_LEVEL
      value: "error"

With this update, Argo CD accepts the wildcard values in the sourceNamespaces field so that you can specify multiple namespaces or patterns for namespaces. To use this feature, specify the namespaces where Argo CD can manage applications in the .spec.sourceNamespaces field of the ArgoCD CR. GITOPS-3935

apiVersion: argoproj.io/v1alpha1
kind: ArgoCD
metadata:
  name: example-argocd-wildcard-pattern
spec:
  sourceNamespaces:
    - app-team-*
   - namespace-2

In the previous example, permissions are granted to namespaces that match the pattern app-team-*, such as app-team-1, app-team-2, and namespace-2, which does not use wildcard values.

To grant permissions for all the namespaces on the Argo CD cluster using the * wildcard pattern, configure the ArgoCD CR in the following manner:

apiVersion: argoproj.io/v1alpha1
kind: ArgoCD
metadata:
  name: example-argocd-all-namespaces
spec:
  sourceNamespaces:
    - '*'

There is currently a known issue that changes the functionality of routing in the OpenShift Console Dynamic plugin, dynamic-console-sdk, that is used by the Red Hat OpenShift GitOps Dynamic Plugin. This issue causes the horizontal navigation bar, which is used to switch between the Application Overview page and the Deployment History page for an application, on the Application Overview page to not function correctly. GITOPS-4232

Workaround: To view the Deployment History page of an application, use the Deployment History link on the application instead of the link on the horizontal navigation bar on the Application Overview page. This issue has been observed on all supported cluster versions that use the Red Hat OpenShift GitOps Dynamic Plugin.

There is currently a known issue on the OpenShift Container Platform cluster for the console Red Hat OpenShift GitOps Dynamic Plugin where users can experience some delay when fetching application data. GITOPS-4234

Workaround: No workaround currently exists for this issue, so you must wait for the fetching of the application data to complete.

There is currently a known issue that causes the Red Hat OpenShift GitOps Dynamic Plugin to be disabled on the OpenShift Container Platform 4.15 cluster. GITOPS-4231

Workaround: Perform the following steps:

With this update, you can selectively disable the redis and application-controller components for an Argo CD instance in a specified namespace. These components are enabled by default. To disable a component, set the enabled flag to false in the .spec.<component>.enabled field of the Argo CD Custom Resource (CR). GITOPS-3723

For example:

apiVersion: argoproj.io/v1alpha1
kind: ArgoCD
metadata:
  name: example-argocd
spec:
  controller:
    enabled: false
  redis:
    enabled: false