DEBUG: Draft: mattermost update to 9.1.0-bb.0

Package Merge Request

Package Changes

(Describe Package changes here)

Package MR

big-bang/product/packages/mattermost!156 (merged)

For Issue

Closes big-bang/product/packages/mattermost#89 (closed)

added botmr mattermost statusreview labels

assigned to @montgomery.marcus

marked this merge request as ready

changed title from Draft: mattermost update to 9.1.0-bb.0 to DEBUG: Draft: mattermost update to 9.1.0-bb.0

changed the description

requested review from @michaelmartin, @chris.oconnell, @ryan.thompson.44, and @ryan.j.garcia

@rgsjustins @andrewshoell : You have been tagged in this merge request for the purpose of conducting secondary review.

added fluentbit label

changed milestone to %2.14.0

added 1 commit

• 7874fe5a - Enable fluentbit

Compare with previous version

minio and postgres are on old versions

@andrewshoell I asked the code owners about this and @cwilliams68067 said:

Why are we swapping our images here?

image: registry1.dso.mil/ironbank/opensource/minio/minio:RELEASE.2023-06-19T19-52-50Z became image: registry1.dso.mil/ironbank/opensource/minio/minio:RELEASE.2023-10-25T06-33-25Z-ubi9
the semver is different, since -ubi9 marks it as being a slightly different flavor of deployment. same thing with postgres12

the -ubi9 one uses registry1.dso.mil/ironbank/redhat/ubi/ubi9-minimal:9.2 as a base while the normal 12.16 postgresql12 uses  registry1.dso.mil/ironbank/redhat/ubi/ubi8:8.8 as a base

We can migrate stuff but each image is usually tailored at some point to include libraries and env variables focused to its use case

Just wanted to make sure we really need to update them.

i'd defer to the codeowners, i just noticed they were old and thought it'd be worth taking a look at

added 1 commit

• 0f71db91 - enable fluentbit through tests/test-values.yaml

Compare with previous version

added statusdoing label and removed statusreview label

changed milestone to %2.15.0

Closing in favor of !3392 (merged)

closed

removed milestone %2.15.0