To get Sentry back up last night, I went through the deployments/statefulsets for all the Sentry dependencies that were using bitnami images and swapped them to bitnamilegacy. With zookeeper-clickhouse I additionally needed to change the tag to :3.8.0-debian-11-r9 as the :3.8.0-debian-10-* tag wasn't available under bitnamilegacy

We need to update the Sentry helm values to override the container image repo/tag values to match these so they don't get reverted next time we deploy changes to the cluster. This is a quick fix vs something more drastic like upgrading to the latest Sentry helm chart that we should do regardless of future plans for Sentry as it should only take a few minutes and without it we're liable to accidentally bring Sentry back down if we need to deploy any changes to anything else in the cluster