4cd7a5d544
When the app.starlingx.io/component label was added to pods it was decided that it would be controlled by a values.yaml key labels:isApplication and its default value was set to "false" [1] and [2]. This should be changed to "true" since all pods created by the stx-openstack charts are related to the stx-openstack app. Additionally, according to LP #2052539 this new label was mixing memory usage metrics and wrongly triggering platform alarms for "Memory threshold exceeded". [1] https://review.opendev.org/c/starlingx/openstack-armada-app/+/903918 [2] https://review.opendev.org/c/starlingx/openstack-armada-app/+/904128 TEST PLAN: PASS - Build openstack-helm package PASS - Build openstack-helm-infra package PASS - Build stx-openstack application tarball PASS - Upload/Apply stx-openstack application (AIO-DX) PASS - No alarms triggered after application is applied Closes-Bug: 2052539 Change-Id: I6e3e99b48c65d6c1730eca2f85b9d700dd6b1ef9 Signed-off-by: Thales Elero Cervi <thaleselero.cervi@windriver.com> |
||
---|---|---|
.. | ||
debian | ||
files | ||
Readme.rst |
Readme.rst
This repo is for https://github.com/openstack/openstack-helm-infra
Changes to this repo are needed for StarlingX and those changes are not yet merged. Rather than clone and diverge the repo, the repo is extracted at a particular git SHA, and patches are applied on top.
As those patches are merged, the SHA can be updated and the local patches removed.