Deploying helm v3 charts with multiple resources defined results in constant deletion + recreation of resources

[glentakahashi]

When using helm v3 (doesn't happen with v2) with multiple resources defined per yaml, kots will continuously try to recreate and destroy resources in those yaml files.
https://kubernetes.io/docs/concepts/cluster-administration/manage-deployment/#organizing-resource-configurations

Example:
For this config:

apiVersion: rbac.authorization.k8s.io/v1beta1
kind: Role
metadata:
  name: kernel-manager
rules:
  - apiGroups:
      - ""
    resources:
      - pods
    verbs:
      - get
      - list
      - create
      - update
      - patch
      - delete
---
kind: ClusterRole
apiVersion: rbac.authorization.k8s.io/v1beta1
metadata:
  name: kapprover
rules:
  - apiGroups: ["certificates.k8s.io"]
    resources: ["certificatesigningrequests"]
    verbs: ["get", "list", "delete", "watch"]
  - apiGroups: ["certificates.k8s.io"]
    resources: ["certificatesigningrequests/approval"]
    verbs: ["update"]
  - apiGroups: [""]
    resources: ["pods", "services"]
    verbs: ["list"]

This is what appears in the Kots "view files"

And every time a new release is triggered, this is the diff always, even if the files haven't changed at all: