Tempo mTLS STRICT
Package Merge Request
Package Changes
https://repo1.dso.mil/platform-one/big-bang/apps/sandbox/tempo/-/blob/0.15.1-bb.2/CHANGELOG.md https://repo1.dso.mil/platform-one/big-bang/apps/sandbox/tempo/-/blob/0.15.1-bb.3/CHANGELOG.md
Package MR
https://repo1.dso.mil/platform-one/big-bang/apps/sandbox/tempo/-/merge_requests/20 https://repo1.dso.mil/platform-one/big-bang/apps/sandbox/tempo/-/merge_requests/22
For Issue
Closes https://repo1.dso.mil/platform-one/big-bang/bigbang/-/issues/1183
BB Processes
Add labels for affected packages so that they are deployed in CI as well as a status label:
Be sure to assign to yourself:
Once it is ready for review switch the status and assign reviewers:
Merge request reports
Activity
- A deleted user
added statusreview tempo labels
assigned to @project_2872_bot2
requested review from @micah.nagel, @BrandenCobb, and @ryan.j.garcia
assigned to @ronwebb
- Resolved by Branden Cobb
Looks like mTLS breaks the tests for tempo.
❌ One or more tests failed for tempo-tempo --- Logs for tempo-script-test: --- --- Running test.sh... --- Hitting tempo /ready endpoint... curl: (56) Recv failure: Connection reset by peer real 0m1.024s user 0m0.010s sys 0m0.010s curl returned exit code 56, see above for error message and curl's elapsed wait time (timeout is 360s) ---
Probably need to update test-values.yaml virtualservices not services.
added statusdoing label and removed statusreview label
mentioned in merge request !1774 (closed)
added statusreview label and removed statusdoing label
removed review request for @ryan.j.garcia
changed milestone to %1.37.0