Yep, that's on me, sorry, I squeezed the changes in during my break and hoped that CI would catch any mistakes.

Brooke Lew (4a104334) at 19 Mar 01:48

@grigoristh All changes should be in!

Brooke Lew (b0cab4b6) at 17 Mar 17:15

Brooke Lew (27bb1c94) at 17 Mar 17:15

... and 4 more commits

Oh good catch! I'm slightly annoyed and honestly a little unsettled that slipped by me.

Somewhat relieved to hear that hahah, was not looking forward to editing dozens of files!

Regarding the using with instead of if, I used it because I noticed that the other sections in the file were using the if style method. Would you like me to pop over and update those sections too while I'm here?

Brooke Lew (39c67aff) at 13 Mar 22:56

Some possibly unaddressed issues

All changes (including non-blocking ones) should be in, thanks!

Brooke Lew (22dfab07) at 13 Mar 22:45

Brooke Lew (7a74179e) at 13 Mar 22:44

... and 186 more commits

Job logs now seem to be duplicated with the flag on, one line with timestamps and one line without.

2026-02-09T14:49:47.742584373+11:00 $ echo Release changelog will be:
2026-02-09T14:49:47.742635651+11:00 Release changelog will be:
2026-02-09T14:49:47.742900817+11:00 $ GITLAB_HOST=$CI_SERVER_URL glab changelog generate --version ${CHART_VERSION} || true
$ echo Release changelog will be:
Release changelog will be:
$ GITLAB_HOST=$CI_SERVER_URL glab changelog generate --version ${CHART_VERSION} || true
2026-02-09T14:49:49.211308805+11:00           
2026-02-09T14:49:49.211308805+11:00    ERROR  
2026-02-09T14:49:49.211308805+11:00           
2026-02-09T14:49:49.213302819+11:00   404 Not Found.                                                                                                      
2026-02-09T14:49:49.213302819+11:00 
2026-02-09T14:49:49.217385624+11:00 $ echo "Releasing on ${CI_COMMIT_TAG}"
2026-02-09T14:49:49.217428680+11:00 Releasing on 2.0.0
2026-02-09T14:49:49.217769809+11:00 
2026-02-09T14:49:49.217769809+11:00 {"command_exit_code": 0, "script": "/scripts-13-2509/step_script"}
          
   ERROR  
          
  404 Not Found.

Any recommendations on how to handle it? Sorry, I've not got much experience with ArgoCD/GitOps, my K8s experience is mostly limited to my tiny Raspberry Pi cluster. I'm thinking of emitting a simple warning if RevisionHistoryLimit is defined for versions <= 1.32. Ideally the warning would only be emitted if the value was changed from the previous revision but that would unnecessarily complicate the chart, and 1.32 is EOL in 3 weeks (28 Feb) anyways. Additionally I think for production environments Gitaly is usually deployed outside of K8s.

@v1ctorr_ Hi, I've submitted an MR for this, but could you clarify what you said about StatefulSets supporting revisionHistoryLimit starting from v1.33 onwards? I found references to it in the 1.23 docs.

What does this MR do?

Allows configuring revisionHistoryLimits for the chart's Deployments and StatefulSets.

Related issues

Closes #6253

Author checklist

For general guidance, please follow our Contributing guide.

Required

For anything in this list which will not be completed, please provide a reason in the MR discussion.

• Merge Request Title and Description are up to date, accurate, and descriptive.
• MR targeting the appropriate branch.
• MR has a green pipeline.
• Documentation created/updated.
• Tests added/updated, and test plan for scenarios not covered by automated tests.
• Equivalent MR/issue for omnibus-gitlab opened.

Reviewers checklist

• MR has a green pipeline on https://gitlab.com/gitlab-org/charts/gitlab.
• Consider downstream impact to the Operator, as per evaluating impact from changes to GitLab chart.

Brooke Lew (eb715cdb) at 05 Feb 00:01

Brooke Lew (87e92c57) at 04 Feb 23:45

Brooke Lew (bcb4f054) at 04 Feb 23:32