UNCLASSIFIED - NO CUI

Skip to content

Update dependency https://repo1.dso.mil/big-bang/bigbang.git to v2.5.0

bigbang bot requested to merge renovate/big-bang into main

This MR contains the following updates:

Package Update Change
https://repo1.dso.mil/big-bang/bigbang.git minor 2.1.0 -> 2.5.0

Release Notes

big-bang/bigbang

v2.5.0

Compare Source

  • !2.5.0; List of merge requests in this release.

v2.4.1

Compare Source

Release Notes - 2.4.1

Please see our documentation page for more information on how to consume and deploy BigBang.

Upgrade Notices
Patch Notes

There are two changes included in this release:

Gitlab:

  • Starting with chart version 7 (app version 16) Gitlab now requires Postgresql 13 or greater and Redis 6 or greater so ensure your Databases are updated to 13.X or 14.X and external elasticache are on version 6 or 7 before upgrading to this version. (BigBang gitlab chart's in-namespace redis is already at version 7, though please read below).
  • If utilizing the in-cluster in-namespace gitlab Database this is not supported for direct upgrades, you will need to perform a pg_dump of the gitlabhq_production database, delete the postgresql statefulset, upgrade and then restore your database.
  • If utilizing the in-cluster in-namespace redis installation from gitlab, the statefulsets for master and replica (if configured) will need to be delete minutes prior to upgrading or else redis communication in-namespace will be broken.
kubectl delete statefulset -n gitlab gitlab-redis-master
  • Be sure to review the list of deprecated features and be sure your pipelines and other post-install portions of Gitlab are not using variables or settings that have been removed in this version.

Loki:

  • The BigBang Loki package's default schema_config settings under the hood were previously pushed with an incorrect date. If you set your own date as mentioned in the 2.4.0 release notes you will be fine, this will mostly affect installations which have not set a custom schema_config or not upgraded to 2.4.0 yet.

Other upgrade notices from 2.4.0 are included here for your convenience. To view the full list of changes make sure to check the 2.4.0 release notes page.

Known Issues

Gitlab 16 transition requires manual updates before deployment. Ensure that all blockers and breaking changes (located above in the patch notes) are addressed prior to release.

Helpful Links

As always, we welcome and appreciate feedback from our community of users. Please feel free to:

Future

Don't see your feature and/or bug fix? Check out our epics for estimates on when you can expect things to drop, and as always, feel free to comment or create issues if you have questions, comments, or concerns.

v2.4.0

Compare Source

  • !2.4.0; List of merge requests in this release.

v2.3.0

Compare Source

  • !2.3.0; List of merge requests in this release.

v2.2.0

Compare Source

  • !2.2.0; List of merge requests in this release.

Configuration

📅 Schedule: At any time (no schedule defined).

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

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

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

  • If you want to rebase/retry this MR, click this checkbox.

This MR has been generated by Renovate Bot.

Edited by bigbang bot

Merge request reports

UNCLASSIFIED - NO CUI