Adding features like serviceAccountName for OpenShift security constraints

[computate]

parent 9cc5541
author Christopher Tate computate@computate.org 1677561053 -0700 committer Christopher Tate computate@computate.org 1677684028 -0700

• fix a bug with postgresql.enabled value
• add docs for new serviceAccountName value for required security on OpenShift
• allow customizing the postgresqlDatabase value and PGDATABASE environment variable on the betydb container
• allow disabling the creation of a betydb Secret in order to use an ExternalSecret from a vault instead

[computate]

@robkooper I noticed I didn't have a value for serviceAccount.enabled, so I added it in addition to serviceAccount.create and set them both to false by default:

serviceAccount:

  # Specifies whether a service account should be added to the deployment
  enabled: false

  # Specifies whether a service account should be created
  create: false

  # Annotations to add to the service account
  annotations: {}

  # The name of the service account to use.
  # If not set and create is true, a name is generated using the fullname template
  name: ""

[robkooper]

Let me update my pr for postgres to update the documentation as pointed out by @infotroph and I can merge both.