鈩癸笍 Hi all, I added a new issue, and associated PR, to the Arize Phoenix repository regarding a recent change in the Helm deployment's ConfigMap. Essentially, the ConfigMap is gating the individual database ENVs in such a way that end-users are forced to deploy the Bitnami PostgreSQL chart, even when the end-user's goal was actually to configure Phoenix to use a self-hosted database (i.e., AWS RDS, Zalando Postgres Operator, etc.). This fix un-gates the ENVs in the ConfigMap to allow for self-hosted database variables, without the Bitnami deployment. I tested the changes on K3s, and everything is working again.
