Which chart:
mongodb-sharded

Describe the bug
The values.yaml file defines priorityClassName in multiple locations for the different types of pods required for a sharded deployment. However, when deploying the chart priorityClassName set, the pods are not configured with a priority class name. There is no way to set priorityClassName without modifying the chart.

Upon inspection of the templates I found nothing regarding priorityClassName. As a comparison, the mongodb chart does allow for setting the priorityClassName.

To Reproduce

1. Define a priority class or use one of the Kubernetes built-in classes (e.g. system-node-critical)
2. Create an override values file with:

shardsvr:
  dataNode:
    priorityClassName: system-node-critical
  arbiter:
    priorityClassName: system-node-critical

configsvr:
  priorityClassName: system-node-critical

mongos:
  priorityClassName: system-node-critical

3. Deploy the chart with the above overrides and run kubectl describe pod on any of the pods. You will see priorityClassName is not set.

Expected behavior
I would expect to see pods deployed with the priorityClassName set to the value defined in the override yaml.