Splunk deployment to configure another splunk instance started by the Splunk operator (Example: add user)

splunk-configurator.yaml

apiVersion: apps/v1
kind: Deployment
metadata:
  name: splunk-configurator
spec:
  selector:
    matchLabels:
      app.kubernetes.io/name: splunk-configurator
  replicas: 1
  template:
    metadata:
      labels:
        app.kubernetes.io/name: splunk-configurator
    spec:
      containers:
        - name: splunk-configurator
          image: splunk/splunk:8.2.8
          command: ["sudo", "-E", "/bin/sh", "-c"]
          env:
            - name: URI
              value: "https://splunk-my-server-standalone-service:8089"
          args:
            - SPLUNK_START_ARGS=--accept-license SPLUNK_PASSWORD=changeme /sbin/entrypoint.sh start-and-exit;
              while true;
              do CRED=admin:$(cat /mnt/splunk-secrets/password);
              /opt/splunk/bin/splunk add user rest -password test -role rest -auth ${CRED} -uri ${URI};
              sleep 60;
              done;
          volumeMounts:
            - mountPath: /mnt/splunk-secrets
              name: mnt-splunk-secrets
      volumes:
        - name: mnt-splunk-secrets
          secret:
            secretName: splunk-default-secret

@raghukumarc yes, you could also connect and run commands manually, but the idea is that you don't have to do this. Your configuration (here your add user commands) should be in this splunk-configurator.yaml - then the splunk-configurator container will run your configuration commands periodically to ensure the configuration. The advantage is that by doing it this way you can keep your configuration in your Git repo. If you need help with that, you can contact my company (https://schiesser-it.com/)

Now I understand. I will get in touch with you in case we need any professional help. Thank you, @marcusschiesser.