ignoreDifferences with DeploymentConfig

[wouter2397]

Hello ArgoCD community,

One of our internal clients is syncing a DeploymentConfig, which is a specific OpenShift manifest.
When applying this ArgoCD starts spamming new replication controllers as the image digest keeps changing to the configured one in GIT.

So I tried to ignore the diff in the container image, but it looks like ArgoCD cannot work with the DeploymentConfig.
Does anyone of you have the same problems?

I'm applying the following code to the AppProject:

ignoreDifferences:
  - group: apps.openshift.io/v1
    kind: DeploymentConfig
    jsonPointers:
      - /spec/template/spec/containers/0/image

[jannfis]

Hi @wouter2397, I think there's a happy little mistake in that configuration, in that the group should be configured without the version specifier. The correct configuration that should work would be:

ignoreDifferences:
  - group: apps.openshift.io
    kind: DeploymentConfig
    jsonPointers:
      - /spec/template/spec/containers/0/image

[jannfis]

Oh, and re-reading about the reason why you'd want that - Re: new replication controllers:

This is a Kubernetes behavior, and not related to Argo CD at all. While I'm not very familiar with OpenShift's DeploymentConfig, you might want to have a look whether setting revisionHistoryLimit is supported (as with K8s standard Deployment resources): https://kubernetes.io/docs/concepts/workloads/controllers/deployment/#clean-up-policy

Ultimately, this controls how many previous versions of ReplicaSet resources will be kept in history.

[wouter2397]

@jannfis Oh, your right! Totally missed that one...
I changed the configuration and indeed it's working now.

Thank you for answering my question on this short notice!