[dependency-track] Expose more configuration options for postgresql chart

[sqdk]

We are hitting a small issue with the postgres DB not requesting enough CPU. I understand that most users might be running a separate psql, but it would be convenient to be able to configure the subchart in cases where the bundled one is enough.

I'm not a helm expert, but based on what I could read in the docs, it should be enough to just add everything from the postgresql chart's values.yaml and put it in the values file for Dependency Track.

If you can confirm that this is a good idea, and that my approach seems sound, I'll happily create a PR with the change.

Is your feature request related to a problem? Please describe.
I cannot pass values to the postgresql subchart. More specifically resource requests and limits for the chart.

Describe the solution you'd like
I can pass values to the postgresql subchart

Describe alternatives you've considered
I could deploy the postgresql chart separately, but in my case, i just need to tweak the resources.

[jorikseldeslachts]

+1

[stoopman]

I would like to see a nodeSelector option for the postgresql service. My cluster has windows nodepools (next to linux nodepools) and when no nodeSelector is specified, deployments end up there by default

[mikesindieiev]

Dependency-track chart uses upstream postgresql chart, so to specify the nodeSelector or nodeAffinity just pass those values directly to the the upstream chart.

To achieve that just add to your values.yaml the following:

postgresql:
  enabled: true
  persistence:
    enabled: true
    existingClaim: "pg-dtrack-1c"
  primary:
    nodeSelector:
      topology.ebs.csi.aws.com/zone: us-east-1c

To check all available fields download the proper version of the chart, unarchive it and review the values.yaml for postgresql

helm repo add dtrack https://raw.githubusercontent.com/bitnami/charts/eb5f9a9513d987b519f0ecd732e7031241c50328/bitnami
helm pull dtrack/postgresql --version 10.10.3
tar -zxvf postgresql-10.10.3.tgz