-
Notifications
You must be signed in to change notification settings - Fork 266
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
kubernetes 1.9.4 breaking universal forwarder with ConfigMap #70
Comments
@mchene ^ |
@erks I've alerted PM and got ack back that they will triage. |
@halr9000 if you're okay with doing |
Any updates? Any temporary fix or work-around? |
@rayh0001 |
Thanks @ffscl
And still reference any file with $SPLUNK_HOME |
Thanks @ffscl @guilhemmarchand that seems to work |
This definitely should be documented. @halr9000 |
@guilhemmarchand Works like a charm!! |
@ffscl That worked like a charm! Thank goodness I found this otherwise I might have gone crazy. |
Sorry I am not getting what solved the issue here... I updated daemonset yaml with:
But nothing seems to work. Please let me know what exactly need to be done to resolve the issue |
@sharmmoh1983 If you are using Splunk Cloud, you need to mount the ConfigMap to |
Can't get this to work with a |
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 thechown
commands inentrypoint.sh
.See: https://answers.splunk.com/answers/626964/kubernetes-194-breaking-changes-universal-forwarde.html
The text was updated successfully, but these errors were encountered: