Skip to content

volumeClaimTemplates triggers persistent Out-of-Sync status in GitOps (ArgoCD) #1103

@arcanez

Description

@arcanez

What version were you using?

NATS Helm Chart 2.12.3

What environment was the server running in?

kind via ArgoCD

Is this defect reproducible?

helm template ./helm/charts/nats --show-only templates/stateful-set.yaml --set config.jetstream.enabled=true

Given the capability you are leveraging, describe your expectation?

  volumeClaimTemplates:
  - apiVersion: v1
    kind: PersistentVolumeClaim
    metadata:
      name: release-name-nats-js
    spec:
      accessModes:
      - ReadWriteOnce
      resources:
        requests:
          storage: 10Gi

Given the expectation, what is the defect you are observing?

  volumeClaimTemplates:
  - metadata:
      name: release-name-nats-js
    spec:
      accessModes:
      - ReadWriteOnce
      resources:
        requests:
          storage: 10Gi

k8s will helpfully add the missing apiVersion & kind upon admission, but causes a drift between what is applied and what is deployed

Metadata

Metadata

Assignees

No one assigned

    Labels

    defectSuspected defect such as a bug or regression

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions