Upgrade Redis to v7.2

We are currently shipping Redis v7.0.15, which has reached EOL in July 2024. Upgrading to v7.2 would give us some additional time to decide on our direction forward https://gitlab.com/gitlab-org/omnibus-gitlab/-/issues/8466+.

Acceptance criteria

• Upgrade Omnibus gitlab-org/omnibus-gitlab!8226 (merged)
• Upgrade GitLab Chart
  • Redis 7.0: gitlab-org/charts/gitlab!3977 (merged)
  • Redis 7.2: gitlab-org/charts/gitlab!4182

added group::distributionbuild groupdistribution typemaintenance labels

added Category:Build sectioninfrastructure platforms labels

changed the description

changed milestone to %17.10

added priority1 label

@denisra - Based on the discussion, I think this issue needs to be done sooner than later.

thanks for all the details @plu8 . @balasankarc and I have been talking about this and we've included this task into our Q1 planning.

@dmakovey Could we adapt gitlab-org/charts/gitlab!3977 (merged) to target redis 7.2 or should we do this in another MR?

sure, we can bump version further in Resolve "Upgrade Redis Chart to version 7.x" (gitlab-org/charts/gitlab!3977 - merged)

Update: gitlab-org/charts/gitlab!3977 (merged) bumped towards Redis 7.0 instead of 7.2, because of compatbility issues between newer redis charts and our current postgresql chart: gitlab-org/charts/gitlab!3977 (comment 2370353731).

This happens because our redis and postgresql chart have a common dependency (bitnami/common).

For a newer redis chart version, we also need to update the psql chart.

Follow-up: Update Redis from 7.0 to 7.2 (gitlab-org/charts/gitlab!4182)

mentioned in merge request gitlab-org/charts/gitlab!3977 (merged)

mentioned in commit gitlab-org/omnibus-gitlab@72e854ee

mentioned in merge request gitlab-org/omnibus-gitlab!8226 (merged)

mentioned in commit gitlab-org/omnibus-gitlab@199769f7

mentioned in commit gitlab-org/omnibus-gitlab@a546016c

Omnibus (workflowin dev): Update Redis from 7.0.15 to 7.2.7 (gitlab-org/omnibus-gitlab!8226 - merged)

mentioned in commit gitlab-org/charts/gitlab@a780f682

changed milestone to %17.11

added missed:17.10 label

something to keep in mind: https://gitlab.com/gitlab-org/omnibus-gitlab/-/issues/8466#note_2400652704

This is going to become a problem. In fact it did for Sidekiq recently with it's 8.0 release where they bumped the minimum support of Redis to 7.2 but then had to quickly rescind that due to this limitation from AWS.

mentioned in commit gitlab-org/charts/gitlab@9eab86b6

mentioned in merge request gitlab-org/charts/gitlab!4182

marked the checklist item Upgrade Omnibus as completed

changed the description