Since apps are using postgres independently of presto (via the hive metastore database), the helm chart should include the community supported postgres chart with an abstraction service that can be pointed to either that containerized deployment and a cloud version.
Once this is in place, the presto chart should no longer deploy postgres and should instead look for the service address of the postgres deployment (which will either be the containerized chart version or the cloud version).
In the event an adopter implements a different storage backend than PrestoDB, this will prevent the removal of the hive metastore's postgres database from impacting the other apps using postgres for brook state.
Since apps are using postgres independently of presto (via the hive metastore database), the helm chart should include the community supported postgres chart with an abstraction service that can be pointed to either that containerized deployment and a cloud version.
Once this is in place, the presto chart should no longer deploy postgres and should instead look for the service address of the postgres deployment (which will either be the containerized chart version or the cloud version).
In the event an adopter implements a different storage backend than PrestoDB, this will prevent the removal of the hive metastore's postgres database from impacting the other apps using postgres for brook state.