SKIP UPGRADE CHECK thanos update to 17.4.0-bb.0
Package Merge Request
Package Changes
https://repo1.dso.mil/big-bang/product/packages/thanos/-/blob/17.4.0-bb.0/CHANGELOG.md
Package MR
big-bang/product/packages/thanos!151 (merged)
For Issue
Closes big-bang/product/packages/thanos#127 (closed)
Upgrade Notices
Thanos was converted to the Big Bang passthrough pattern. Any values intended for the upstream Bitnami Thanos chart must now live under thanos.values.upstream instead of directly under thanos.values.
e.g.
addons:
thanos:
enabled: true
values:
upstream:
query:
enabled: true
compactor:
enabled: trueThanos upstream chart dependency is now vendored locally
This MR updates the aliased upstream Bitnami Thanos chart from 17.3.1 to 17.4.0, but the more important maintenance change is that the upstream chart is no longer pulled
from Bitnamis OCI registry.
Bitnami no longer publishes the Thanos chart to the OCI source previously referenced by this package, so the package now uses a vendored local chart tarball instead:
- Previous dependency source:
oci://registry-1.docker.io/bitnamicharts - New dependency source:
file://./charts - Vendored artifact:
chart/charts/thanos-17.4.0.tgz
Impact
This change should not require any deployment-time values changes for Big Bang consumers.
The impact is for package maintainers:
- Do not use
helm dependency update ./chartto refresh the upstreamthanosdependency anymore. - Future Thanos chart upgrades must be performed by manually vendoring the updated upstream Bitnami chart tarball into
chart/charts/and updatingchart/Chart.yamlandchart/Chart.lockaccordingly. docs/DEVELOPMENT_MAINTENANCE.mdhas been updated to document the new workflow.
Action required
- End users: no action required beyond normal validation for the Thanos chart update and upstream value nesting.
- Maintainers: follow the new manual vendored tarball workflow documented in
docs/DEVELOPMENT_MAINTENANCE.mdfor future upstream Thanos chart updates.