Hi all,
I would like to bring to your attention an helpful improvment giving the possibility to set the storageclass definition and the secret directly on file values.
In our case we need to create sc definition and secret applying custom yaml files after the installation of ceph-csi-rbd by helm chart.

Below are the versions of chart and appl. used in our environment based on k8s 1.9.1:
appl

Is your feature request related to a problem? Please describe.
Add unit test for NodeExpand

Describe the solution you'd like
[A clear and concise description of what you want to happen.]

• Move crds from templates to crds which is the recommended way for installing crds using helm3

• Add template/crds.yaml with

  {{- if .Values.installCRDs }}
  {{- range $path, $bytes := .Files.Glob "crds/*.yaml" }}
    {{ $.Files.Get $path }}
  ---
  {{- end }}
  {{- end

What

Encrypt volumes provisioned by topolvm

How

eg. LUKS

Generate per-PVC encryption keys, stored as Kubernetes secrets.

The threat this would mitigate is physical theft of server (as keys are only kept in memory)