Using ConfigMap to manage splunk universal forwarder's config has been working well until the release of 1.9.4, which included this security fix.
ConfigMap now gets mounted as read-only always, which breaks this container due to the chown commands in entrypoint.sh.
See: https://answers.splunk.com/answers/626964/kubernetes-194-breaking-changes-universal-forwarde.html