Extract the cost management deployment component specifications from the clowdapp manifest and extend the existing helm chart in ros-helm-chart repo to include these components. Ensure all cost and ros components are successfully deployed when creating or updating the chart and provide a test script for integration validation similar to the test-ocp-dataflow-jwt.sh script that validates the successful deployment of the ros components in OCP.

Note that due to the resource requirements (trino alone consumes at least 2Gb of memory) to cost management deployments, this chart will only be operational in an OCP cluster and not in kind, so there is a dependency to have the openshift-ci available in the ros-helm-chart repo for this purpose.

The koku image has been custom built and pushed to quay.io/insights-onprem/koku as it is not possible to pull from the upstream version due to access restrictions.

The chart must include support for the same security aspects as it is in the current chart for ros components to enable the cost management metrics operator and the UI to be able to interact with the services.