You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
we have built a custom bitnami image (using UBI9 with FIPS enabled) , now we would like to use this custom image with latest bitnami chart , need to change md5 to scram-sha-256 in pg_hba.conf file
What is the feature you are proposing to solve the problem?
Can you please help us with easy way to change md5 to scram-sha-256 in pg_hba.conf file ,(Is there any extra environment that we can set in the bitnami containers ?)
What alternatives have you considered?
No response
The text was updated successfully, but these errors were encountered:
javsalgar
changed the title
How to enable FIPS on postgresql bitnami chart?
[bitnami/postgresql] How to enable FIPS on postgresql bitnami chart?
Sep 24, 2024
The Bitnami Application Catalog (OpenSource) is built on Debian 12. As part of VMware, Bitnami also provides a custom catalog of containers and Helm Charts based on various base images, including Debian 11 & 12, PhotonOS 5, Ubuntu 22.04 & 24.04, and Red Hat UBI 8 & 9. You can explore these options via the VMware Tanzu Application Catalog.
Beyond the variety of distributions, the VMware Tanzu Application Catalog offers enterprise-grade features such as FIPS, VEX, SBOM, and SLSA3. If you have any further questions, feel free to reach out.
Name and Version
bitnami/postgresql
What is the problem this feature will solve?
we have built a custom bitnami image (using UBI9 with FIPS enabled) , now we would like to use this custom image with latest bitnami chart , need to change md5 to scram-sha-256 in pg_hba.conf file
What is the feature you are proposing to solve the problem?
Can you please help us with easy way to change md5 to scram-sha-256 in pg_hba.conf file ,(Is there any extra environment that we can set in the bitnami containers ?)
What alternatives have you considered?
No response
The text was updated successfully, but these errors were encountered: