From 51e2c3d129e85d6a2a057a0dc3c8db9f17731973 Mon Sep 17 00:00:00 2001 From: AkshayDubey29 Date: Tue, 17 Jul 2018 16:07:37 +0530 Subject: [PATCH] Update README.md --- universalforwarder/README.md | 13 +++++++++++++ 1 file changed, 13 insertions(+) diff --git a/universalforwarder/README.md b/universalforwarder/README.md index d8f7903..fa8f317 100644 --- a/universalforwarder/README.md +++ b/universalforwarder/README.md @@ -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: