627c1d30e7
Since most customers do not need this audit, the chart will be
disabled by default, which will prevent an unnecessary periodic
CrobnJob from being triggered. But the customer's can choose to
enable the audit via the 'system helm-chart-attribute-modify'
if desired.
system helm-override-list platform-integ-apps -l
system helm-chart-attribute-modify --enabled true \
platform-integ-appsceph-pools-audit kube-system
system helm-chart-attribute-modify --enabled false \
platform-integ-apps ceph-pools-audit kube-system
system application-apply platform-integ-apps
Additionally, the cephfs and rbd storage-init scripts have been
changed to set the 'min_size' of their respective pools.
Finally, the ceph-pools-audit chart was a CronJob and was replaced
by a Deployment to avoid processing spikes every time the job was
executed. And also the audit script was optimized to execute the
minimum number of ceph commands.
NOTE: This chart will be disabled for new upload/applies only
(i.e. initial installs). If already have a version applied, it
will use whatever is set in the 'system helm-override-list'
command.
PS: The patch 0017 has been removed and the change has
been made directly in the patch 0008, as it is a new
file (template) created by us, not upstream.
Test Plan:
PASS: On a fresh install, apply the app and check if
the chart is disabled
PASS: Check the chart status with
'system helm-override-list platform-integ-apps -l',
update the app and confirm again to see if it remains
the same.
PASS: Change backend capabilities (replication, min_replication)
and check if the pools have been changed.
* Tests were performed on AIO-SX/AIO-DX with k8s v1.29
Story: 2011353
Task: 51825
Depends-On: https://review.opendev.org/c/starlingx/config/+/943688
Change-Id: Id86ee8902fbc860917725741f86097c196a894fd
Signed-off-by: Erickson Silva de Oliveira <Erickson.SilvadeOliveira@windriver.com>
k8sapp-platform
This project contains StarlingX Kubernetes application specific python plugins for the platform integration application. These plugins are required to integrate the application into the StarlingX application framework and to support the various StarlingX deployments.