Currently every component has his own values.yaml without any prefix for the values.
As we using the concept of one big joined values.yaml with the recommended defaults at KKP, see charts/values.example.ee.yaml, we should use it at the user cluster MLA component as well.
It makes it for customer easier to manage the different values customizations and as we are on the beginning of the project, it should be a good time for doing it.
E.g. at one customer, we already have 5 customized values files to manage, this could get reduced
Currently every component has his own
values.yamlwithout any prefix for the values. As we using the concept of one big joinedvalues.yamlwith the recommended defaults at KKP, seecharts/values.example.ee.yaml, we should use it at the user cluster MLA component as well.It makes it for customer easier to manage the different values customizations and as we are on the beginning of the project, it should be a good time for doing it. E.g. at one customer, we already have 5 customized values files to manage, this could get reduced