Skip to content

Conversation

@jmsplunk
Copy link
Collaborator

@jmsplunk jmsplunk commented Jan 7, 2026

Description

Add the spec defaultkvstoretype to the CRDs. Later ansible will check the env variables and update the server.conf in the instance.

Key Changes

  • Add the defaultkvstoretype in the common spec
  • The ENV will pick up the spec and update the env variable
  • The ansible will check the env variables and update the server.conf in the instance. (not implemented yet)

Testing and Verification

Deployed a standalone using

cat <<EOF | kubectl apply -n splunk-operator -f -
apiVersion: enterprise.splunk.com/v4
kind: Standalone
metadata:
  name: test-kvstore
  namespace:  splunk-operator
spec:
  replicas: 1
  defaultKVStoreType: "externalManaged"
EOF

and we can see it accepts the spec and can find it in the env

root@ip-10-236-5-61:~/splunk-operator# kubectl get pods -n splunk-operator
NAME                                                  READY   STATUS    RESTARTS   AGE
splunk-operator-controller-manager-68f7cf68f8-wl9ch   1/1     Running   0          56s
splunk-test-kvstore-standalone-0                      0/1     Running   0          23s
  
  
root@ip-10-236-5-61:~/splunk-operator# kubectl describe pod splunk-test-kvstore-standalone-0 -n splunk-operator | grep SPLUNK_KVSTORE_TYPE
      SPLUNK_KVSTORE_TYPE:                           externalManaged

Related Issues

Jira tickets, GitHub issues, Support tickets...

PR Checklist

  • Code changes adhere to the project's coding standards.
  • Relevant unit and integration tests are included.
  • Documentation has been updated accordingly.
  • All tests pass locally.
  • The PR description follows the project's guidelines.

@jmsplunk jmsplunk self-assigned this Jan 7, 2026
@patrykw-splunk
Copy link
Collaborator

Hey, please add description and rest of necessary fields

@jmsplunk jmsplunk closed this Jan 8, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants