Using ArgoCD (v2.13.2) to install Sumologic in an EKS cluster (v1.30) using the official chart (v4.13.0) causes the application to never be in sync because the current chart does not add kind nor apiVersion to volumeClaimTemplates to statefulsets (otelcol-events and otelcol-logs)
The cluster will automatically add this fields to the created object, creating an a drift impossible to fix, expect with Argo's ignoreDifferences, which is not ideal.
Current deployed state:
volumeClaimTemplates:
- apiVersion: v1
kind: PersistentVolumeClaim
metadata:Desired state by ArgoCD:
volumeClaimTemplates:
- metadata:
The chart should add the fields kind and apiVersion to the volumeClaimTemplates helm template, so sumologic can show as synced on ArgoCD without the ignore clause.
Using ArgoCD (v2.13.2) to install Sumologic in an EKS cluster (v1.30) using the official chart (v4.13.0) causes the application to never be in sync because the current chart does not add
kindnorapiVersiontovolumeClaimTemplatesto statefulsets (otelcol-events and otelcol-logs)The cluster will automatically add this fields to the created object, creating an a drift impossible to fix, expect with Argo's
ignoreDifferences, which is not ideal.Current deployed state:
Desired state by ArgoCD:
The chart should add the fields
kindandapiVersionto thevolumeClaimTemplateshelm template, so sumologic can show as synced on ArgoCD without the ignore clause.