chore: services version bump

[saidsef]

No description provided.

[saidsef]

/code review

[saidsef]

🤖

README.md

• Line 1: The addition of "(LGTM)" after the list of technologies is unclear without context. If "LGTM" is an established acronym for these technologies, this change is acceptable. Otherwise, it might confuse readers.
• Line 42: The change from "Grafana Stack" to "LGTM Stack" should be consistent with the previous change. Ensure that the new term "LGTM Stack" is widely understood or provide a brief explanation.

deployment/loki/statefulset.yml

• Line 29: Updating the Loki image from 2.9.4 to 2.9.5 is a minor version bump, typically indicating bug fixes or minor improvements. Ensure this version has been tested for compatibility with the rest of the stack.

deployment/prometheus/deployment.yml

• Line 25: The Prometheus image update from v2.50.0 to v2.50.1 is also a minor version bump. Similar to Loki, ensure compatibility and testing have been conducted.

deployment/promtail/daemonset.yml

• Line 24: Upgrading Promtail from 2.9.4 to 2.9.5 follows the same logic as the Loki update. Ensure this version is compatible with the version of Loki being used.

deployment/tempo/cm.yml

• Line 51-54: The comment and the version update from vParquet2 to vParquet3 suggest performance improvements and new features. Verify that this change is supported by the rest of the stack and that any new requirements (e.g., for TraceQL structural operators) are met.

deployment/tempo/statefulset.yml

• Line 24: Updating Tempo from 2.3.1 to 2.4.0 indicates new features or improvements. As with other version bumps, ensure this has been tested for compatibility.

General Notes

• All version updates should be tested in a staging environment before deployment to production to ensure there are no compatibility issues.
• The change in terminology in the README.md should be clearly communicated to all stakeholders to avoid confusion.

_{> gpt-4-turbo-preview}