[chart] 0.9.6 StorageClass Missing YAML Document Separator

[aballman]

/kind bug

What happened?
When using the storageClasses field in the helm chart and providing multiple entries, the generated yaml does not include the document separator ---

# Source: aws-ebs-csi-driver/templates/storageclass.yaml
kind: StorageClass
apiVersion: storage.k8s.io/v1
metadata:
  name: sc1
provisioner: ebs.csi.aws.com
volumeBindingMode: WaitForFirstConsumer
kind: StorageClass
apiVersion: storage.k8s.io/v1
metadata:
  name: sc2
provisioner: ebs.csi.aws.com
volumeBindingMode: WaitForFirstConsumer

What you expected to happen?
The same yaml is generated with the document separator, so that N resources are created instead of 1.

# Source: aws-ebs-csi-driver/templates/storageclass.yaml
kind: StorageClass
apiVersion: storage.k8s.io/v1
metadata:
  name: sc1
provisioner: ebs.csi.aws.com
volumeBindingMode: WaitForFirstConsumer
---
kind: StorageClass
apiVersion: storage.k8s.io/v1
metadata:
  name: sc2
provisioner: ebs.csi.aws.com
volumeBindingMode: WaitForFirstConsumer

How to reproduce it (as minimally and precisely as possible)?
Using the following for your values

storageClasses:
- name: "sc1"
- name: "sc2"

Anything else we need to know?:
Nope

Environment

• Kubernetes version (use kubectl version): 1.18.9 EKS
• Driver version: 3.0.3
• Chart version: 0.9.6

[ayberk]

/good-first-issue

[k8s-ci-robot]

@ayberk:
This request has been marked as suitable for new contributors.

Please ensure the request meets the requirements listed here.

If this request no longer meets these requirements, the label can be removed
by commenting with the /remove-good-first-issue command.

In response to this:

/good-first-issue

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[nvnmandadhi]

I'd like to help with this, I'd be looking to change the Storageclass template, right?

[nvnmandadhi]

/assign

[krmichel]

@ayberk looks like PR #762 was merged but not connected to this issue. Looks like it can be closed.

[ayberk]

/close

[k8s-ci-robot]

@ayberk: Closing this issue.

In response to this:

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.