This PR closes https://github.com/rstudio/helm/issues/422 by providing customers guidance on how to configure and set database passwords consistently and in a Kubernetes-friendly way across products.
The docs added show how to configure the database and set up PostgreSQL database passwords as env variables from K8s secrets in Workbench, Connect and Package Manager. This is now possible since Workbench supports setting the database password as an env variable in the 2024.04.0 release (Connect and Package Manager already supported this).
Currently, admins need to either set the password in the values or imperatively during helm install. Both are not very k8s native ways of doing things.
After this, I will file PRs to each product's admin guide to make instructions consistent there. With license file and database passwords being pulled from secrets admins no longer need to set any custom values during helm install which is very nice!
This PR closes https://github.com/rstudio/helm/issues/422 by providing customers guidance on how to configure and set database passwords consistently and in a Kubernetes-friendly way across products.
The docs added show how to configure the database and set up PostgreSQL database passwords as env variables from K8s secrets in Workbench, Connect and Package Manager. This is now possible since Workbench supports setting the database password as an env variable in the 2024.04.0 release (Connect and Package Manager already supported this).
Currently, admins need to either set the password in the values or imperatively during
helm install. Both are not very k8s native ways of doing things.After this, I will file PRs to each product's admin guide to make instructions consistent there. With license file and database passwords being pulled from secrets admins no longer need to set any custom values during
helm installwhich is very nice!