Gitops tools keep reporting CRDs as out-of-sync due to status field

[abyth]

Describe the bug CRDs contain status information that are subject to change once they are applied to a cluster. Gitops tools like argo-cd detect those changes and mark the entries as out-of-sync

Steps to reproduce the issue:

• Install argo-cd e.g. as described here https://argoproj.github.io/argo-cd/getting_started/
• Deploy the banzaicloud kafka-operator using helm:

  apiVersion: argoproj.io/v1alpha1
  kind: Application
  metadata:
  name: kafka-operator
  namespace: argocd
  spec:
  destination:
  namespace: kafka
  server: https://kubernetes.default.svc
  project: default
  source:
  path: charts/kafka-operator
  repoURL: https://github.com/banzaicloud/kafka-operator.git
  targetRevision: v0.12.0
  syncPolicy:
  automated: {}

• Check the argo-cd web-ui and check the kafka-operator application

Expected behavior CRDs do not contain information that are subject to change, allowing gitops tools like argo-cd to successfully manage them and keep them in-sync

Additional context argo-cd: v1.5.2 kafka-operator: v0.12.0

[stoader]

@abyth Those fields are set by Kubernetes and used to store information about the state if CRD itself (e.g. what versions of the CRD Kubernetes serves in case a resource has multiple versions).

[abyth]

Thanks for your reply. I do understand what the fields are used for - i was just wondering whether or not they have to be part of the definition. Other CRDs we are using feature that field but are not defining it in the CRD resource. Forgot to mention it: We got around the issue by explicitly ignoring the /status field in our application:

  ignoreDifferences:
    - group: apiextensions.k8s.io
      kind: CustomResourceDefinition
      jsonPointers:
      - /status