Best way to perform post-chart configuration/customization

[robert.haskins]

We are deploying Confluence DC via Atlassian Helm Charts, and need to do a little post-helm configuration:

1) add a couple of jar files

2) update a couple of .xml configuration files

3) add one external binary to the container

It's unfortunate that the files I need to change are not on shared home, so this will need to be done on every confluence pod every time the cluster is rebuilt. What is the best way to achieve this? It isn't much, so I am thinking in terms of just using kubctl to copy the files and script in, and run the script, but it seems like there should be a better way.

Does anyone have any suggestions?

[Yevhen]

@robert.haskins it depends on the files. I suggest you take a look at additionalFiles and additionalConfigMaps in values.yaml. With additionalFiles, you can either create configmaps/secrets outside Helm and have them mounted into containers, or you can define additionalConfigMaps with keys and content, and helm chart will create them for you and mount them to the specified locations.