Skip to content
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

fix(argo-cd): Upgrade redis to last version to get security fixes #998

Closed
wants to merge 1 commit into from

Conversation

mtparet
Copy link

@mtparet mtparet commented Oct 26, 2021

Signed-off-by: Matthieu Paret matthieu.paret@lifen.fr

Note on DCO:

If the DCO action in the integration test fails, one or more of your commits are not signed off. Please click on the Details link next to the DCO action for instructions on how to resolve this.

Checklist:

  • I have bumped the chart version according to versioning
  • I have updated the chart changelog with all the changes that come with this pull request according to changelog.
  • Any new values are backwards compatible and/or have sensible default.
  • I have signed off all my commits as required by DCO.
  • My build is green (troubleshooting builds).

Changes are automatically published when merged to master. They are not published on branches.

Signed-off-by: Matthieu Paret <matthieu.paret@lifen.fr>
@mtparet mtparet changed the title Upgrade redis to last version to get security fixes fix(argo-cd): Upgrade redis to last version to get security fixes Oct 26, 2021
@mbevc1
Copy link
Collaborator

mbevc1 commented Oct 26, 2021

Thanks for you contribution. Seems like upstream still runs 6.2.4.
https://github.com/argoproj/argo-cd/blob/master/manifests/base/redis/argocd-redis-deployment.yaml#L24
Chart is trying to keep defaults the same, but you can always manually bump this in the deployment.

@mbevc1 mbevc1 added the argo-cd label Oct 26, 2021
@mkilchhofer
Copy link
Member

Duplicates #916

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.

3 participants