Duplicate Node Selector on Cluster Auditor Deployment

Description: There is a duplicate nodeSelector configuration in the deployment template for cluster-auditor (one that is hard coded via the template and one that accepts values from the values file):

• cluster-auditor deployment issue
• When specifying a nodeSelector via the values file, the deployment will produce a deployment yaml with two nodeSelector values.

Error:. The is the following error from Flux:

• Helm upgrade failed: error while running post render on files: map[string]interface {}(nil): yaml: unmarshal errors: line 92: mapping key "nodeSelector" already defined at line 32