Chapter 1. Red Hat OpenShift GitOps release notes

With this update, Red Hat OpenShift GitOps supports the addition of extra volumes and volume mounts to the ApplicationSet Controller components. You can configure these additional resources by specifying the .spec.applicationSet.volumes and .spec.applicationSet.volumeMounts fields in the Argo CD Custom Resource (CR). GITOPS-5739

apiVersion: argoproj.io/v1beta1
kind: ArgoCD
metadata:
  name: argocd-example
spec:
  applicationSet:
    volumes:
      - name: <volume_name> 
        emptyDir: {} 
    volumeMounts:
      - name: <volume_name> 
        mountPath: <mount_path> 

apiVersion: argoproj.io/v1beta1
kind: ArgoCD
metadata:
  name: argocd-example
spec:
  applicationSet:
    volumes:
      - name: <volume_name> 

        emptyDir: {} 

    volumeMounts:
      - name: <volume_name> 

        mountPath: <mount_path> 

With this update, users can add custom labels and annotations to the server, repo-server, applicationset-controller, and application-controller pods. This enhancement improves observability for external systems that depend on resource labels or annotations for monitoring purposes. The following fields are introduced in the Argo CD CR to support this functionality:

For more information, see Custom Annotations and Labels. GITOPS-5674

Before this update, users could not configure some replicas for the Argo Rollouts controller by using the RolloutManager custom resource (CR). With this update, high availability (HA) support is introduced by adding a new .spec.ha field to the RolloutManager CR.

When you enable high availability, the GitOps Operator automatically sets the number of replicas to 2, the leader election is activated, and default anti-affinity rules are applied to ensure redundancy and reliability. GITOPS-5622

With this update, you can now use Kubernetes TLS-type secrets to configure custom TLS certificates for Routes in the Argo CD CR. Previously, TLS data had to be embedded directly in the Argo CD CR as plain text, which could pose security risks due to the sensitive nature of TLS information.

To enhance security, you must use Kubernetes secrets to manage TLS data. The following fields are introduced in the Argo CD CR to reference Kubernetes secrets of type kubernetes.io/tls containing TLS data:

For more information about configuring a route for custom TLS certificate, see examples in Custom TLS certificates for Routes. GITOPS-5232

With this update, the Sources tab in the Details panel of a multi-source application now includes two new buttons:

GITOPS-4175

With this update, users can now enable or disable the Argo Rollouts UI in Argo CD instances by setting a new boolean field, enableRolloutsUI, in the server component of the Argo CD CR. GITOPS-3604

apiVersion: argoproj.io/v1beta1
kind: ArgoCD
metadata:
  name: argocd
spec:
  server:
    enableRolloutsUI: true 

apiVersion: argoproj.io/v1beta1
kind: ArgoCD
metadata:
  name: argocd
spec:
  server:
    enableRolloutsUI: true