tempo update to 1.23.3-bb.0
Package Merge Request
Package Changes
https://repo1.dso.mil/big-bang/product/packages/tempo/-/blob/1.23.3-bb.0/CHANGELOG.md
Package MR
big-bang/product/packages/tempo!187 (merged)
For Issue
Closes big-bang/product/packages/tempo#120 (closed)
Upgrade Notices
Upgrades from < 1.21.1-bb.3
If you are upgrading from a Tempo package version earlier than 1.21.1-bb.3, you must also account for the breaking changes introduced in 1.21.1-bb.3. Please review the 1.21.1-bb.3 Upgrade Notices.
In summary:
-
Passthrough refactor: all package-specific values that were previously under
tempo:must be moved undertempo.values.upstream:. Big Bang–specific top-level keys such asdomain,sso,istio,networkPolicies,bbtests, andwaitJobremain at the top level and are not moved.Example:
Previous values:
tempo: repository: registry1.dso.mil/ironbank/opensource/grafana/tempo tag: 2.7.2 pullPolicy: IfNotPresentUpdated values:
tempo: values: upstream: repository: registry1.dso.mil/ironbank/opensource/grafana/tempo tag: 2.7.2 pullPolicy: IfNotPresent -
Upgrade job for immutable StatefulSet: enabling
upgradeJob.enabled=truedeploys a Helm pre-upgrade job that deletes and recreates thetempo-tempoStatefulSet to handle immutable field changes. A brief outage is expected while thetempo-tempopods roll.
Upgrades to 1.23.3-bb.0 – Tempo Port Change (3100 -> 3200)
The pod annotation traffic.sidecar.istio.io/includeInboundPorts has been removed from the tempo-tempo pods and requires a pod restart to take effect. When upgrading directly from <1.21.1-bb.3 to 1.23.3-bb.0, the upgradeJob introduced in 1.21.1-bb.3 (if enabled) should also take care of restarting the Tempo pods so they pick up the annotation changes and new port configuration in the 1.23.3-bb.0 release.
Operators should verify that the tempo-tempo pods have been restarted; if not, restart the pods for the Tempo StatefulSet (for example, with kubectl rollout restart statefulset tempo-tempo -n tempo) before considering the upgrade complete.