kubernetes 1.9.4 breaking universal forwarder with ConfigMap about docker-splunk-legacy HOT 13 OPEN

@rayh0001
Mount your config maps inside /var/opt/splunk/etc instead of directly inside ${SPLUNK_HOME}. This fix works because the entrypoint copies the files over before trying to change the ownership https://github.com/splunk/docker-splunk/blob/master/universalforwarder/entrypoint.sh#L24

from docker-splunk-legacy.

Thanks @ffscl
I just tested it in a Kubernetes v1.10.2 cluster and this fixes the issue, I used:

        volumeMounts:
        - name: ufconfig
          mountPath: /var/opt/splunk/etc/apps/search/local

And still reference any file with $SPLUNK_HOME

from docker-splunk-legacy.

Sorry I am not getting what solved the issue here... I updated daemonset yaml with:

volumeMounts:
        - name: ufconfig
          mountPath: /var/opt/splunk/etc/apps/search/local

But nothing seems to work. Please let me know what exactly need to be done to resolve the issue

from docker-splunk-legacy.

@sharmmoh1983 If you are using Splunk Cloud, you need to mount the ConfigMap to /var/opt/splunk/etc/apps/splunkclouduf/default

from docker-splunk-legacy.

@mchene ^

from docker-splunk-legacy.

@erks I've alerted PM and got ack back that they will triage.

from docker-splunk-legacy.

@halr9000 if you're okay with doing chown ... || true, which seems to work for me, I can create a quick PR for that.

from docker-splunk-legacy.

Any updates? Any temporary fix or work-around?

from docker-splunk-legacy.

Thanks @ffscl @guilhemmarchand that seems to work

from docker-splunk-legacy.

This definitely should be documented. @halr9000

from docker-splunk-legacy.

@guilhemmarchand Works like a charm!!

from docker-splunk-legacy.

@ffscl That worked like a charm! Thank goodness I found this otherwise I might have gone crazy.

from docker-splunk-legacy.

Can't get this to work with a daemonset and configmaps. Does anyone has any working example with splunkforwarder:7.3.0 ?

from docker-splunk-legacy.