Feature: Inject custom manifest configuration
Motivation
Claudie deploys some manifests, predominantly the Longorn, with sane defaults. However, there's currently no way how to customize them. This approach falls short (e.g. when using taints) or when the user would like to change the configuration of Longhorn or other Claudie-deployed components.
Description
Propose a way how to customize manifests that are being applied by Claudie's kuber service on the Claudie-made clusters.
Exit criteria
- [ ] Propose an architecture that allows over-riding the default configs
- [ ] Ensure that this approach is extendable to LBs in the future (the implementation will be done with another task though)
- [ ] Implement the proposal
One thing to keep in mind here is: How is updates handled if the user has customized config files, and Claudie has added new config values or changed some. Is documentation on new/changed config values enough? Or can there be some smart way of "merging"?
Hi @Danielss89 , thank you for raising this. In fact we're about to design a solution so that these customizations are respected no matter to what happens to the clusters (upgrades, changes, etc.). There are several design options, and we need to choose the one that will fit us the best long-term. We'll keep you posted.