v0.1.0

This release updates to Argo CD 2.1.6, as well as updating the operator-sdk framework used to 1.11.0

Enhancements

• #290 - feat: Reconcile argocd-repo-server-tls volume mounts
• #303 - feat: Reconcile on change of argocd-repo-server-tls and implement AutoTLS feature
• #316 - feat: Configure Keycloak SSO for Argo CD Instance
• #326 - feat: Enable service CA for reencrypt routes to argocd-server on OpenShift
• #346 - allow operator to manage permissions based on namespace labels
• #358 - Add ability to specify Repo server image and tag
• #360 - feat: Add ability to apply additional labels to generated routes
• #362 - feat: Add the ability to specify additional kustomize versions within the ArgoCD ConfigMap
• #371 - feat: Add ability to configure loglevel for each ArgoCD component
• #384 - feat: Add ability to shard application controller
• #387 - feat: Add log format for ArgoCD components
• #406 - Upgrade operator-sdk to 1.10.0
• #410 - feat: add NodeSelector and Tolerations in argo crd
• #415 - feat: Allow setting ARGOCD_EXEC_TIMEOUT in repo server
• #429 - chore: upgrade operator-sdk to v1.11.0
• #432 - feat: Add support to restrict login to optional list of groups using Dex
• #437 - feat: Allow setting custom environment in Argo CD workloads
• #444 - feat: Make parallelism limit configurable and set default to 10

Fixes

• #287 - fix: volume mount argocd-gpg-keys-cm to repo server pods
• #291 - ApplicationSet controller not mounting ArgoCD secrets to access repositories through SSH
• #305 - fix: add compute resources to init containers
• #331 - Add owner reference to the cluster secret
• #364 - fix: Allow reconciliation of resource overrides
• #366 - fix: Allow ArgoCD CR to override keycloak resource request/limit defaults
• #367 - fix: Keycloak fails to update OIDC config in argocd-cm intermittently
• #368 - fix: delete existing RBACs when namespace label is updated
• #372 - fix: operator crashes on reconciliation when existing Argo CD configmap is empty
• #376 - fix: ArgoCD server resources limit/request changes in ArgoCD CR are not reconcilied
• #378 - fix: ApplicationSet controller Deployment reconcilliation update logic misses volume field
• #389 - fix: Operator errors on reconciling namespaces, Cannot list resource namespaces
• #401 - fix: Make parallelism limit configurable and set default to 10
• #413 - fix: Only set ownerReferences for roles & rolebindings in CR's namespace
• #414 - fix: Do not copy all labels from ArgoCD CR to resources we create
• #417 - FIX: remove RBACs from target-namespace when ArgoCD instance is deleted
• #421 - fix: Do not restart argocd-server on changes to argocd-tls
• #428 - fix: upgrade ingress to networking/v1
• #434 - fix: Remove trailing newline from admin.password
• #440 - Fix: managed-by label reset to source namespace
• #442 - fix: log error and update status when both dex and keycloak are configured
• #446 - fix: Invalid Image location for ApplicationSets
• #449 - fix: add nodePlacement check in applicationSet reconciler
• #452 - fix: Keycloak deployments do not respect NodeSelector and Tolerations in the Argo CD CR
• #453 - fix: Changing log level/format triggers reconciliation
• #454 - Update applicationset crd to v0.2.0
• #465 - fix: reposerver, server and controller pods restart continuously when multiple env vars are set

Note that due to the upgrade of the operator-sdk version, the operator itself no longer creates a ServiceMonitor CR to expose the operator's default metric (This does not affect the metrics exposed by Argo CD itself). To expose the operator's default metrics, create the following CR in the namespace where the operator is installed

apiVersion: monitoring.coreos.com/v1
kind: ServiceMonitor
metadata:
  labels:
    control-plane: controller-manager
  name: argocd-operator-controller-manager-metrics-monitor
spec:
  endpoints:
  - bearerTokenFile: /var/run/secrets/kubernetes.io/serviceaccount/token
    path: /metrics
    port: https
    scheme: https
    tlsConfig:
      insecureSkipVerify: true
  selector:
    matchLabels:
      control-plane: controller-manager

v0.0.15

This release includes the following enhancements, bug fixes and documentation updates.

Enhancements

• #184 - Add Property to Disable Admin User
• #194 - Add support for proxies in the repo-server deployment
• #280 - Add support for Argo CD 2.0.

Bug Fixes

• #186 - Pods stuck in crashloop after update to 0.0.14
• #187 - Fix issue with replacing the resource configuration
• #191 - Missing gpg configmap after update argocd-operator 0.0.13 to 0.0.14

Documentation

• #189 - Add documentation for the resourceInclusions property
• #190 - Fixed port-forward command
• #195 - Fixed wrong TLS key example for server route

v0.0.14

This release includes the following enhancements, bug fixes and documentation updates.

Enhancements

• #148 - Add support for Argo CD 1.7.
• #144 - Add option to control resync frequency for argocd application controller.
• #167 - Support cert-utils-operator with the CA generation.

Bug Fixes

• #122 - Fix reconciliation of argocd-tls-certs-cm.
• #151 - Fix for not updating when changing the ArgoCD resource
• #152 - Fix OLM version mismatch/initialSSHKnownHosts validation error.
• #162 - Don't rereconcile deleted ArgoCD objects.

Documentation

• #140 - Update example with how to enable Routes.
• #156 - Fix a mistake in the Routes documentation with password retrieval.
• #173 - Document a small nuanced issue with group mappings.

v0.0.13 Release

This release continues the use of Argo CD v1.6.1 and includes the following enhancements:

• Updates to Server TLS Secret Should Sync With Argo Secret
• Add Properties for Redis HAProxy Component to control image/tag
• Allow users to either include/exclude the default ssh hosts that are included with ArgoCD by default

v0.0.12 Release

This release continues the use of Argo CD v1.6.1 and includes the following enhancements:

• Update operator-sdk Dependency to v0.18.0
• Share ServiceAcount for Redis Components

v0.0.11 Release

This release includes the following enhancements and bug fixes:

Enhancements

• Update to Argo CD v1.6.1
• Allow mounting of ServiceAccountToken / specifying of ServiceAccount in Repo Server
• Ability to utilize repository.credentials in initialRepositories

Bug Fixes

• Handle upgrades for all Argo CD components

v0.0.10 Release

This release updates Argo CD to v1.5.8 and includes the following:

⚠️ BREAKING CHANGE NOTICE ⚠️

The ArgoCD custom resource has breaking changes to the Ingress and Route properties.

Ingress: The Spec.Ingress property has been removed from the ArgoCD custom resource. The Spec.Grafana.Ingress, Spec.Prometheus.Ingress and Spec.Server.Ingress properties have all been converted from a boolean value to an object that allows for more customization of the Ingress resource for those components that are managed by the operator. The following shows the old and new way of defining Ingress options.

OLD

apiVersion: argoproj.io/v1alpha1
kind: ArgoCD
metadata:
name: example-argocd
spec:
    ingress:
        host: myhost
        path: /mypath
    server:
        grpc:
            ingress: true
        ingress: true
        insecure: true

NEW

apiVersion: argoproj.io/v1alpha1
kind: ArgoCD
metadata:
    name: example-argocd
spec:
    server:
        grpc:
            ingress:
                enabled: true
        host: myhost
        ingress:
            enabled: true
            path: /mypath
            tls:
                secretName: my-secret
        insecure: true

Routes: The Spec.Grafana.Route, Spec.Prometheus.Route and Spec.Server.Route properties have all been converted from a boolean value to an object that allows for more customization of the Route resource for those components that are managed by the operator. The following shows the old and new way of defining Route options.

OLD

apiVersion: argoproj.io/v1alpha1
kind: ArgoCD
metadata:
    name: example-argocd
spec:
    grafana:
        enabled: true
        route: true
    prometheus:
        enabled: true
        route: true
    server:
        route: true

NEW

apiVersion: argoproj.io/v1alpha1
kind: ArgoCD
metadata:
    name: example-argocd
spec:
    grafana:
        enabled: true
        route:
            enabled: true     
    prometheus:
        enabled: true
        route:
            enabled: true
    server:
        host: myhost
        route:
            enabled: true
            path: /mypath
            tls:
                termination: passthrough
                insecureEdgeTerminationPolicy: Redirect
            wildcardPolicy: None

New Features

• Add options to customize Ingress and Route resources managed by the operator. See breaking change notice above.
• The operator will now report the status for each component on the ArgoCD custom resource. In addition the Phase status property will be updated by looking at the following components.
  • Argo CD Application Controller
  • Redis
  • Repo Server
  • Argo CD Server
• Generate OLM artifacts using the new OLM bundle format. Currently both formats are supported until the old format is retired.

Bug Fixes

• Fixed bug in the naming of Argo CD server Ingress resources that prevented the Argo CD URL from being set correctly.

v0.0.9 Release

This release includes the following along with several documentation updates.

• Update Operator to Argo CD v1.5.5
• Add Support for Backups to an Azure Storage Container
• Add Support for Backups to a GCP Bucket
• Upgrade operator-sdk to v0.17.0

v0.0.8 Release

This release contains the following bug fixes.

• Only Initialize Repos, SSH Known Host and Certs
• Rename Cluster Secret to Avoid Name Collisions
• Allow Override of Host on Routes
• Trigger Rollout for Dex when Configuration Changes

v0.0.7 Release

This release updates the operator to deploy Argo CD v1.5.2, which addresses CVE-2020-5260.

See the following for more information:

• GHSA-qm7j-c969-7j4q
• https://github.com/argoproj/argo-cd/releases/tag/v1.5.2