Skip to content

chore(deps): update helm release redis to v21 #52

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented May 6, 2025

This PR contains the following updates:

Package Update Change
redis (source) major 17.13.2 -> 21.1.4

Release Notes

bitnami/charts (redis)

v21.1.4

  • [bitnami/redis] ⚡ ⬆️ Update dependency references (#​33767)

v21.1.3

v21.1.2

v21.1.1

v21.0.3

v21.0.2

  • [bitnami/redis] chore: ♻️ ⬆️ Update common and remove k8s < 1.23 references (#​33428) (98dff1d), closes #​33428

v21.0.0

v20.13.4

v20.13.2

v20.13.1

v20.13.0

v20.12.2

  • [bitnami/redis] fix 32573 - Always announce hostname independent of external service configuration ( (282ae5c), closes #​33024

v20.12.1

v20.12.0

  • [bitnami/redis] Support retrieving Redis ACL user passwords from Kubernetes Secrets (#​32434) (e4fd127), closes #​32434

v20.11.5

v20.11.4

v20.11.3

v20.11.2

v20.11.1

v20.11.0

v20.10.1

v20.10.0

v20.9.0

v20.8.0

v20.7.1

v20.7.0

v20.6.3

  • [bitnami/redis] fix: update JSON schema to allow string values for values passed to tpl (#​30526) (2c78a06), closes #​30526

v20.6.2

v20.6.1

v20.6.0

v20.5.0

v20.4.1

v20.4.0

v20.3.0

v20.2.2

v20.2.1

v20.2.0

v20.1.7

v20.1.6

v20.1.5

v20.1.4

v20.1.3

v20.1.2

v20.1.1

v20.1.0

v20.0.5

v20.0.4

v20.0.3

v20.0.2

v20.0.1

v20.0.0

v19.6.4

v19.6.3

v19.6.2

v19.6.1

v19.6.0

v19.5.5

v19.5.4

v19.5.3

v19.5.2

v19.5.1

v19.5.0

v19.4.0

v19.3.4

v19.3.3

v19.3.2

v19.3.1

v19.3.0

v19.2.0

v19.1.5

v19.1.4

v19.1.3

v19.1.2

v19.1.1

v19.1.0

v19.0.2

  • allow to set containerSecurityContext on kubectl container to fix issue e.g. with OpenShift (#​24730) (4fda65b), closes #​24730

v19.0.1

v19.0.0

v18.19.4

v18.19.3

v18.19.2

v18.19.1

v18.19.0

v18.18.1

v18.18.0

  • [bitnami/redis] feat: ✨ 🔒 Add automatic adaptation for Openshift restricted-v2 SCC (#​2 (063463f), closes #​24149

v18.17.1

v18.17.0

v18.16.1

v18.16.0

v18.15.1

v18.14.0

v18.13.0

v18.12.1

v18.12.0

  • [bitnami/redis] fix: 🐛 Add allowExternalEgress to avoid breaking istio and fix metrics port (#​22 (2b78bee), closes #​22955

v18.11.1

v18.11.0

v18.10.0

v18.9.1

v18.9.0

v18.8.3

  • [bitnami/redis] Do not create master and replica serviceaccounts when using sentinel (#​22716) (13c6479), closes #​22716

v18.8.2

v18.8.0

v18.7.1

v18.7.0

  • [bitnami/redis] fix: 🔒 Improve podSecurityContext and containerSecurityContext with essential s (2198b3f), closes #​22184

v18.6.4

v18.6.3

v18.6.2

v18.6.1

v18.6.0

v18.5.0

v18.4.0

v18.3.3

v18.3.2

v18.3.1

  • [bitnami/redis] Replace deprecated pull secret partial (#​20666) ([e03531b](https

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), 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.

@renovate renovate bot force-pushed the renovate/redis-21.x branch 3 times, most recently from fd5a5dd to ce65f7e Compare May 15, 2025 15:29
@renovate renovate bot force-pushed the renovate/redis-21.x branch 2 times, most recently from 5a475e4 to f238254 Compare May 16, 2025 19:54
@renovate renovate bot force-pushed the renovate/redis-21.x branch from f238254 to e7ac4b9 Compare May 20, 2025 11:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants