camunda / camunda-platform-helm

Camunda Platform 8 Self-Managed Helm charts
https://docs.camunda.io/docs/self-managed/overview/
Apache License 2.0
74 stars 137 forks source link

[ENHANCEMENT] Add apiVersion and kind to PersistentVolumeClaims #2214

Open aqeelat opened 2 months ago

aqeelat commented 2 months ago

Describe the issue: When managing camunda via argocd, the application always appears out of sync because of this:

image

Actual behavior:

The generated statefulset does not include the full template details https://github.com/camunda/camunda-platform-helm/blob/main/charts/camunda-platform-latest/templates/zeebe/statefulset.yaml#L256

Expected behavior:

How to reproduce:

helm template camunda camunda-platform --repo https://helm.camunda.io --version 10.2.1 > out.yaml

Logs:

Environment:

Please note: Without the following info, it's hard to resolve the issue and probably it will be closed.

jessesimpson36 commented 2 months ago

I think this ticket title and description is specific to argo but this is a more generic problem. kubernetes resources have default values that appear to fill in when you leave off the options inside your manifest, and without us specifying those upstream defaults, CD platforms like flux and argo may say that a reconcile / sync failed.