Attention Iron Bank Customers: On March 27, 2025, we are moving SBOM artifacts from the Anchore Scan job to the Build job to streamline the container hardening pipeline. If you currently download SBOMs from the Anchore Scan job, you can still get them from the Build job and from other sources, including IBFE and image attestations.
Looks like the local postgres database is failing to deploy causing the rest of it to fail as there's no database server. Not sure why the user context has been explicitly set to 26, but setting it to 1001 (tried that manually on the stateful set in a local dev cluster) got it a bit further only for it to fail to initiate the database. I attempted to enable the volumePermission setting per this article https://stackoverflow.com/questions/63283477/helm-postgres-cannot-create-directory, but that did not fix the issue.
bigbang botchanged the descriptionCompare with previous version
Spoke with Ryan on this one and decided to use a more updated version of Postgres 13 as opposed to doing a major upgrade to Postgres 15. Rolled back changes to security context user so it should still be using User 26 at this time.
Jimmy Bourquemarked the checklist item Sync upstream helm chart version with updated dependencies. as completed
marked the checklist item Sync upstream helm chart version with updated dependencies. as completed