Caracal: Update monitoring stack components

[cityofships]

prometheus-alertmanager: 0.27.0 -> 0.28.0
prometheus-blackbox-exporter: 0.24.0 -> 0.25.0
prometheus-cadvisor: 0.49.1 -> 0.49.2
prometheus-elasticsearch-exporter: 1.7.0 -> 1.8.0
prometheus-memcached-exporter: 0.14.2 -> 0.15.0
prometheus-mtail: 3.0.0-rc54 -> 3.0.8
prometheus-mysqld-exporter: 0.15.1 -> 0.16.0
prometheus-node-exporter: 1.7.0 -> 1.8.2
prometheus 2.50.1 -> 2.55.1

Co-authored-by: Piotr Parczewski [email protected]

Change-Id: I9359df23a41a600dd46dbc1812a54be57fd33f71

[dougszumski]

This should be fine. Are we certain that there is no risk during the TSDB schema migration in prometheus 2.50.1 -> 2.55.1 ? Have you tried it? How long does it take on SMS lab?
We don't want to cause any unexpected impact at customer sites. Sorry to be a pain!

For others - the motivation of the backport is to prepare for Prometheus v3.0 in Epoxy, which requires upgrading to Prometheus 2.55.1 first.

[cityofships]

This should be fine. Are we certain that there is no risk during the TSDB schema migration in prometheus 2.50.1 -> 2.55.1 ? Have you tried it? How long does it take on SMS lab? We don't want to cause any unexpected impact at customer sites. Sorry to be a pain!

For others - the motivation of the backport is to prepare for Prometheus v3.0 in Epoxy, which requires upgrading to Prometheus 2.55.1 first.

This change does not directly affect anybody, since we're controlling tags via https://github.com/stackhpc/stackhpc-kayobe-config/blob/stackhpc/2024.1/etc/kayobe/kolla-image-tags.yml. Only after things were tested, we'd bump up versions there.

[dougszumski]

This should be fine. Are we certain that there is no risk during the TSDB schema migration in prometheus 2.50.1 -> 2.55.1 ? Have you tried it? How long does it take on SMS lab? We don't want to cause any unexpected impact at customer sites. Sorry to be a pain!
For others - the motivation of the backport is to prepare for Prometheus v3.0 in Epoxy, which requires upgrading to Prometheus 2.55.1 first.

This change does not directly affect anybody, since we're controlling tags via https://github.com/stackhpc/stackhpc-kayobe-config/blob/stackhpc/2024.1/etc/kayobe/kolla-image-tags.yml. Only after things were tested, we'd bump up versions there.

It still needs testing before merging to the stable branch. Someone might refresh the tags for a security fix etc. without being fully aware of the change. You can make a kayobe config branch, point it at this backports branch and build it via https://github.com/stackhpc/stackhpc-kayobe-config/actions/workflows/stackhpc-container-image-build.yml or just replace the binary directly in the container in this case.

[cityofships]

This should be fine. Are we certain that there is no risk during the TSDB schema migration in prometheus 2.50.1 -> 2.55.1 ? Have you tried it? How long does it take on SMS lab? We don't want to cause any unexpected impact at customer sites. Sorry to be a pain!
For others - the motivation of the backport is to prepare for Prometheus v3.0 in Epoxy, which requires upgrading to Prometheus 2.55.1 first.

This change does not directly affect anybody, since we're controlling tags via https://github.com/stackhpc/stackhpc-kayobe-config/blob/stackhpc/2024.1/etc/kayobe/kolla-image-tags.yml. Only after things were tested, we'd bump up versions there.

It still needs testing before merging to the stable branch. Someone might refresh the tags for a security fix etc. without being fully aware of the change. You can make a kayobe config branch, point it at this backports branch and build it via https://github.com/stackhpc/stackhpc-kayobe-config/actions/workflows/stackhpc-container-image-build.yml or just replace the binary directly in the container in this case.

Fair enough - draft until it's tested.