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> (1)
        emptyDir: {} (2)
    volumeMounts:
      - name: <volume_name> (3)
        mountPath: <mount_path> (4)

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:

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.

With this update, the Argo CD multi-source application functionality in GitOps Operator is promoted from Technology Preview (TP) to General Availability (GA). Use this feature to define and manage applications with multiple source repositories. GITOPS-5511

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.

With this update, Restricted pod security admission (PSA) labels are applied to the openshift-gitops namespace to ensure compliance with OpenShift Container Platform standards. If you are running additional workloads in the openshift-gitops namespace, ensure they comply with restricted PSA requirements. If compliance with restricted PSA is not feasible, use a user-defined, cluster-scoped Argo CD instance. In such instances, PSA labels are not applied or controlled by the GitOps Operator. GITOPS-5221

Before this update, trafficmanagement and metric plugins could not be configured by using the RolloutManager CR in Argo Rollouts. With this update, you can now specify trafficmanagement and metric plugins in the RolloutManager CR. The GitOps Operator automatically updates the config map when these plugin fields are added, modified, or removed. This enhancement allows users to manage trafficmanagement and metric plugins natively through the RolloutManager CR, eliminating the need for manual config map updates. GITOPS-4217

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

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 (1)

With this update, you can access documentation on configuring the ApplicationSet controller in the Argo CD CR to use different policies. For more information, see ApplicationSet Controller policies. GITOPS-5236

Before this update, when the desired state for an existing Ingress changed the host, the new host information was not applied. This update fixes the issue by adding Ingress checks to ensure the Ingress is updated when the host changes. If there is a change in the Ingress host, it will be correctly updated with the new value, ensuring that the desired state is reflected. GITOPS-5386

Before this update, when the desired state for the server service type changes, for example, from ClusterIP to NodePort, the change was not applied automatically to the cluster without first deleting the resource. This update fixes the issue by adding a server service check to apply changes to the server service. If the desired state for the server service type changes, it is applied automatically to the cluster without deleting the resource. GITOPS-5385

Before this update, users were unable to set a custom image for the ApplicationSet Controller after specifying it in the Argo CD CR. This update fixes the issue by allowing users to set a custom image for the ApplicationSet Controller. GITOPS-5395

Before this update, Argo CD was unable to retrieve the correct TLS certificate for Helm OCI registries if the URL contained a path or port number. This update fixes the issue by using a fix in upstream Argo CD that ensures the URL is correctly parsed, allowing Argo CD to retrieve and return a valid TLS certificate. GITOPS-5081