Chapter 1. Red Hat OpenShift GitOps release notes

With this update, the following enhancements have been introduced for multi-source application:

With this update, you can extend the repo server storage by mounting persistent volumes. The repo server utilizes the EmptyDir default storage volume, which has limitations and might prove inadequate in scenarios involving numerous repositories, sizable repositories, or repositories containing large manifests. You can mount additional storage on demand by using the .spec.repo.volumes and .spec.repo.volumeMounts fields in the Argo CD custom resource (CR). GITOPS-4646

For more information, refer to the HA for Repo Server.

With this update, Red Hat OpenShift GitOps provides support for the sidecar and init containers for the Server and Application Controller components. You can configure the sidecar and init containers by using the spec.server.sidecarContainers, spec.controller.sidecarContainers, spec.server.initContainers, and spec.controller.initContainers fields in the Argo CD CR. GITOPS-5010

apiVersion: argoproj.io/v1beta1
kind: ArgoCD
metadata:
  name: example-argocd
spec:
  server:
    initContainers:
    - name: argocd-init
      image: nginx:latest
    sidecarContainers:
    - name: cmp
      image: busybox

With this update, you can expose Argo CD Application labels on Kubernetes events generated by Argo CD. When events are created for applications that have specific label keys defined in the resource.includeEventLabelKeys field within the argocd-cm config map, the controller adds the matching labels to these events. This enhancement facilitates the filtering and processing of events based on the application labels. To set the resource.includeEventLabelKeys field in a GitOps environment, use the .spec.extraConfig field in the Argo CD CR. The GitOps Operator automatically adds these fields from the .spec.extraConfig field into the argocd-cm config map. GITOPS-3233

apiVersion: argoproj.io/v1beta1
kind: ArgoCD
metadata:
  name: argocd-sample 1
  namespace: default 2
spec:
  extraConfig:
    resource.includeEventLabelKeys: team,env* 3

For more information, see Labels on Application Events.

With this update, you can verify commit signatures for ApplicationSet CRD created using Git generators. GITOPS-3049

Before this update, adding a self-signed TLS certificate for the ApplicationSet GitLab SCM Provider did not function as intended, as the certificate failed to mount on the required volume. This update fixes the issue by correcting the volume mount path and providing documentation on the usage of this feature. Users are now required to ensure that the config map’s name is argocd-appset-gitlab-scm-tls-certs-cm. GITOPS-4801

apiVersion: v1
kind: ConfigMap
metadata:
  name: argocd-appset-gitlab-scm-tls-certs-cm 1
  namespace: test-1-32-appsets-scm-tls-mount 2
data:
  cert: |
    -----BEGIN CERTIFICATE-----
    ... (certificate contents) ...
    -----END CERTIFICATE-----

For more information, see Add Self-signed TLS Certificate for Gitlab SCM Provider to ApplicationSet Controller.