Skip to content
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.

Sign up for GitHub

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

Update README.md #85

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
+13 −0
Open

Update README.md #85

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
13 changes: 13 additions & 0 deletions universalforwarder/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -264,6 +264,19 @@ If you use `docker-compose` (or reference an existing volume with `docker run`)
0. Save `docker-compose.yml` and close it.
0. Run `docker-compose up` again.

If you want to configure self signed certificate at forwarder side, you need to follow following steps:-

0. Copy client cert to the current directory
0. Copy root CA certificate to the same directory.
0. Then push the container to the local repository


Now say if you are using Kubernetes to configure splunk forwarder in K8s cluster then you need to set the start arguments like below

- name: SPLUNK_FORWARD_SERVER_ARGS
value: "-ssl-cert-path /opt/splunk/etc/auth/self_signed/myMainServerCertificate.pem -ssl-root-ca-path /opt/splunk/etc/auth/self_signed/myCACertificate.pem -ssl-password ******"


## If you still need help

If you still have trouble forwarding data with the Splunk universal forwarder Docker image, use one of the following options:
Expand Down