[ISSUE] timescaledb-multinode : invalid volume declaration when persistentVolume.enabled is false

[sv5d]

The volume template is invalid in statefulset-timescaledb-datanode.yaml and statefulset-timescaledb-accessnode.yaml when persistentVolume.enabled is false. The volumes: property is missing in the generated yaml.

To Reproduce helm template timescaledb-multinode --set persistentVolume.enabled=false --debug produces invalid Yaml:

      affinity:
        podAntiAffinity:
          preferredDuringSchedulingIgnoredDuringExecution:
          - weight: 100
            podAffinityTerm:
              topologyKey: "kubernetes.io/hostname"
              labelSelector:
                matchLabels:
                  app:  timescaledb
                  release: "RELEASE-NAME"

      - name: storage-volume
        emptyDir: {}

Expected behavior It should produce:

      affinity:
        podAntiAffinity:
          preferredDuringSchedulingIgnoredDuringExecution:
          - weight: 100
            podAffinityTerm:
              topologyKey: "kubernetes.io/hostname"
              labelSelector:
                matchLabels:
                  app:  timescaledb
                  release: "RELEASE-NAME"
      volumes:
      - name: storage-volume
        emptyDir: {}

[paulfantom]

We are sorry to say that multinode helm chart is deprecated and not supported anymore. If you want to see this chart supported then we are looking for community maintainers - https://github.com/timescale/helm-charts/tree/master/charts/timescaledb-multinode#call-for-maintainers

[paulfantom]

I am closing this issue as TimescaleDB-Multinode helm chart is no longer maintained and deprecated. We are looking for potential community maintainers who could help us in getting that helm chart working again. If you wish to become a maintainer, please contact us on slack.

Keep in mind that TimescaleDB is not and will not be dropping multinode setup. Deprecation is only about helm chart.