Helm Chart Improvements

[i5okie]

• Do not create the database secret, use the secret created by PostgreSQL chart itself when enabled.
• Update Values file
• Update _helpers
• Update and clean up Readme

Note: When installing with a custom release name that does not contain "traction", the user must set fullNameOverride.

[github-actions[bot]]

Deployment	Resource	Location
Traction
	Tenant UI	https://pr-1381-traction-tenant-ui-dev.apps.silver.devops.gov.bc.ca
	Innkeeper UI	https://pr-1381-traction-tenant-ui-dev.apps.silver.devops.gov.bc.ca/innkeeper
Aca-Py
	Admin Swagger	https://pr-1381-traction-acapy-admin-dev.apps.silver.devops.gov.bc.ca/api/doc
	Tenant Proxy Swagger	https://pr-1381-traction-tenant-proxy-dev.apps.silver.devops.gov.bc.ca/api/doc

Deployment URLs ready for review.

[i5okie]

Small tweak suggestion.

Also wondering how will migration from existing deployments with the previous version of the chart work: if database users are created with different names we may risk issues when rolling out the new chart. Do we need special steps documented on how to update to this release?

There's no change to the database user names. We are pointing to existing secrets in our deployments in dev, test, and prod. I think PR re-deployments and current deployments will have PostgreSQL create its own secret, which will have to be manually updated with values from the existing secret.

[loneil]

@i5okie fairly standard regression testing of Traction stuff appears to be working as expected on the PR env created here.

[loneil]

Are the changes with https://github.com/bcgov/traction/pull/1342 related or superseded by this one? Wondering if that older PR needs closing or merging.

[i5okie]

Are the changes with #1342 related or superseded by this one? Wondering if that older PR needs closing or merging.

Superseded. I'll close that pr.