feat(container)!: Update image redis to v20

[renovate]

This PR contains the following updates:

Package	Update	Change
redis (source)	major	19.6.4 -> 20.6.1

---

Release Notes

bitnami/charts (redis)

v20.6.1

• [bitnami/redis] Release 20.6.1 (#​31138)

v20.6.0

• [bitname/redis] Add support for master and replicas resources to be annotated (#​31034)

v20.5.0

• [bitnami/redis] Detect non-standard images (#​30942)

v20.4.1

• [bitnami/redis] CA shouldn't be mandatory when TLS is enabled (#​30520) (85219eb), closes #​30520

v20.4.0

• [bitnami/*] docs: 📝 Add "Prometheus metrics" (batch 5) (#​30674) (ed2a546), closes #​30674
• [bitnami/redis] add extraPortsEnabled (#​30607) (77a98fa), closes #​30607

v20.3.0

• [bitnami/redis] feat: ✨ Allow updating credentials via values.yaml (#​30452) (d6a3118), closes #​30452

v20.2.2

• [bitnami/*] Remove wrong comment about imagePullPolicy (#​30107) (a51f9e4), closes #​30107
• [bitnami/redis] Release 20.2.2 (#​30407) (ae54e98), closes #​30407
• Update documentation links to techdocs.broadcom.com (#​29931) (f0d9ad7), closes #​29931

v20.2.1

• [bitnami/redis] Fix preExecCmds parameter (#​29898) (6db8a2e), closes #​29898

v20.2.0

• [bitnami/redis] add extraPodSpec (#​29725)

v20.1.7

• [bitnami/redis] Release 20.1.7 (#​29756)

v20.1.6

• [bitnami/redis] adds kind & apiVersion for pvc template in statefulset (#​29678) (13212d2), closes #​29678

v20.1.5

• [bitnami/redis] - fix additionalEndpoints in servicemonitor (#​29595) (6e674ff), closes #​29595

v20.1.4

• [bitnami/redis] Release 20.1.4 (#​29530) (8053b1a), closes #​29530

v20.1.3

• [bitnami/redis] Release 20.1.3 (#​29411) (b0b5c88), closes #​29411

v20.1.2

• [bitnami/redis] Use common password manager to handle password (#​29376) (6ec3657), closes #​29376

v20.1.1

• [bitnami/redis] fix: move variable from annotation to label (#​29209) (396fa01), closes #​29209

v20.1.0

• [bitnami/redis] Support extraEnvVars on volume-permissions for dynamic subfolders (#​29195) (b33ff20), closes #​29195

v20.0.5

• [bitnami/redis] label slave pod using sentinel masterService (#​29121) (6ae397f), closes #​29121

v20.0.4

• [bitnami/redis] update values.schema.json (#​29106) (8a2fea3), closes #​29106

v20.0.3

• [bitnami/redis] Release 20.0.3 (#​28941) (d2a1abb), closes #​28941

v20.0.2

• [bitnami/redis] Release 20.0.2 (#​28881) (582b058), closes #​28881
• [bitnami/redis] Update README after major update (#​28848) (a96205b), closes #​28848

v20.0.1

• [bitnami/redis] fix: Use rollout restart in ginkgo tests (#​28813) (1d8cb54), closes #​28813

v20.0.0

• [bitnami/redis] Release 20.0.0 (#​28810) (9e08d34), closes #​28810

---

Configuration

📅 Schedule: Branch creation - "on saturday" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[jsaveker]

Here is an automated review from ChatGPT of this pull request.

From the provided git diff, the changes are focused on updating the version of the Redis chart used within a Helm release for a Mastodon deployment on Kubernetes. Specifically, the version is being updated from 19.0.1 to 20.0.1. Without further context on the Redis chart updates themselves or the specific usages within the Mastodon application, it's challenging to identify any explicit security issues purely based on this version increment.

However, considering best practices and potential security implications:

1. Dependencies Update: Regularly updating dependencies, including Helm charts, can be a proactive measure to ensure security vulnerabilities are patched. Thus, this change could potentially be enhancing security by including fixes available in the newer chart version.

2. Version Compatibility: It's crucial to ensure that the new chart version (20.0.1) is fully compatible with the Mastodon application and its specific Redis usage. Incompatibilities can inadvertently introduce stability or security issues.

3. ChangeLog Review: It is important to review the changelog for the new Redis chart version to identify any security fixes, deprecated features, or other changes that might impact the deployment or require further adjustments.

4. Helm Repository Trust: The source repository (bitnami) is a well-known and trusted source for Helm charts. It's always important to ensure that Helm charts are fetched from reputable sources to avoid injecting malicious or compromised charts.

No explicit security issues identified based on the git diff provided.

Suggested actions (not necessarily fixes, since no direct security issues were identified):

- **Review the Redis chart's changelog for version 20.0.1**: Ensure that there are no breaking changes or deprecations that might affect the Mastodon deployment. Pay special attention to any security fixes or vulnerabilities addressed in the new version.

- **Test the Mastodon application with the updated Redis version**: Before deploying to production, thoroughly test the application to ensure compatibility and that no unforeseen issues arise due to the Redis chart update.

- **Continuously monitor the `bitnami` Helm repository and Redis releases**: Stay informed about any further updates or advisories related to the Redis chart to promptly address future vulnerabilities.

Without additional context such as deployment configurations, application-specific Redis usages, or details on the changes introduced in Redis chart version 20.0.1, no more detailed security assessment can be conducted based on this git diff.