Comment 4 for bug 2052539

Just for the sake of documentation: I double checked the stx-* images built from OpenStack "stable/2023.1" branches and as of today five images received cherry-picks since 2023 Dec 18th. I fixed the following images to commit SHAs preceding 2023 Dec 18th as follows:

* stx-cinder: e215be5fc6bcd4cdbc32883d4215a289986e4b01
* stx-horizon: 5ca2d4082900dc51ae85226d903cb0a397f3e225
* stx-keystone: ea8c8aa982235240cf58bd561132aefe33439506
* stx-neutron: 877e85e5a8b8668fc4baf7ee84b71225dadfa647
* stx-nova: 698421064b4604087634f8ea219795dad0b4928c

I tested stx-openstack using the images built from commit SHAs as as peer my previous comment this did not affected the alarm raised, since the memory usage is basically the same.

The problem seems to be related with the introduction of the label "app.starlingx.io/component" to stx-openstack helm-charts, since it was done setting "isApplication: false" by default and is probably misleading the platform metrics on the usage of platform memory.