The Splunk operator supports default.yml by the Parameter defaultUrl
In cases when the default.yml changes, we have to manually kill the pods so that the new settings are applied.
BTW: the same applies to the licenseUrl parameter
Expected behavior
The Splunk Operator should monitor the configmaps, defined in the defaultUrl. If they change, SOK should ensure that the settings are applied right away to the pods that make use of it.
Best Case Scenario: The settings are applied without the restart of the pod. After the new settings are applied by ansible, a simple '/opt/splunk/bin/splunk restart' should be enough.
Splunk setup on K8S
example value file we are using.
we are not facing this issue, as we are using terraform to deploy configurations for kubernetes.
And in tf changing default.yml forces to recreate pod.
Please select the type of request
Bug
Tell us more
Describe the request The Docker Splunk Image allows defining default configurations in configmaps, which are read during startup by the ansible scripts and translated into splunk configs. https://github.com/splunk/docker-splunk/blob/develop/docs/ADVANCED.md#using-defaultyml
The Splunk operator supports default.yml by the Parameter
defaultUrl
In cases when the default.yml changes, we have to manually kill the pods so that the new settings are applied.
BTW: the same applies to the
licenseUrl
parameterExpected behavior The Splunk Operator should monitor the configmaps, defined in the
defaultUrl
. If they change, SOK should ensure that the settings are applied right away to the pods that make use of it. Best Case Scenario: The settings are applied without the restart of the pod. After the new settings are applied by ansible, a simple '/opt/splunk/bin/splunk restart' should be enough.Splunk setup on K8S example value file we are using.