directory hierarchies not being created as Kubernetes configmap correctly

[mmguero]

This was found when testing the release for v23.12.0, but since it is not a regression it didn't hold up that release. It'll be fixed in a subsequent release.

Sub-directories of arbitrary depth are not supported in my creation of configMaps. This means that the subdirectories MISP and STIX and whatever other arbitrary subdirectories there might be in there aren't getting created correctly for Kubernetes.

I need to see what we can do about this.

[mmguero]

So it turns out that configMap does not allow creating defining nested directory hierarchy (see kubernetes/kubernetes#62421, kubernetes/kubernetes#63362). There are some workarounds suggested, like zipping up the directory and unzipping on the other side.

What I decided to do instead can be seen here:

• when creating the configmap
• when starting the container

When creating the data maps for files in a directory, if there is directory structure I name the entry with the special _MALDIR_ replacer in the place of the directory separators. During container startup when we handle the special configmap and secretmap directories, we expand them back out and create the parent directories as needed.

so acid_MALDIR_ACID_MALDIR_s7comm_MALDIR_detect_MALDIR_copy.zeek will be renamed to acid/ACID/s7comm/detect/copy.zeek

This appears to work fine