The loose coupling of the xnat-web sub-chart has presented some unintended outcomes to the long term development of the Helm chart.
Some of these outcomes include:
- Multiple consistency points between value files and documentation increasing deployment overheads.
- Added points within the parent values files for configuration based on deployment considerations.
- Integrations more difficult to make consistent between charts.
To resolve many of these issues the /xnat/charts/xnat-web sub-chart is to be moved to the parent location of /xnat/templates/xnat-web directory. This move provides better/direct access to the other sub-chart values, allows for integration code to be added to xnat-web directly, removes the maintenance of an entire values.yaml and README.md file.
The loose coupling of the xnat-web sub-chart has presented some unintended outcomes to the long term development of the Helm chart.
Some of these outcomes include:
To resolve many of these issues the /xnat/charts/xnat-web sub-chart is to be moved to the parent location of /xnat/templates/xnat-web directory. This move provides better/direct access to the other sub-chart values, allows for integration code to be added to xnat-web directly, removes the maintenance of an entire values.yaml and README.md file.