Customize Splunk Operator settings
Configure the Splunk Operator before or after deployment.
You can customize the Splunk Operator deployment by editing the installation YAML before applying it, or by editing the running deployment after installation. The following table lists the configurable settings.
Configurable settings
| Setting | Description | Default value |
|---|---|---|
| Splunk General Terms | You must accept the Splunk General Terms to start containers. | "" (empty) |
| Watched Namespaces | Manage Splunk Enterprise custom resources in the namespaces identified. If the value is empty, the Splunk Operator watches all namespaces in the cluster. | "" (empty) |
| Docker Image Registries | Set a private registry for the Splunk Operator and Splunk Enterprise images. | splunk/splunk-operator, splunk/splunk |
| Cluster Domain | Override the Kubernetes cluster domain to calculate the fully qualified domain names (FQDN) for each instance. | cluster.local |
| Deployed Namespace | Override the Kubernetes namespace in which to deploy the Splunk Operator. | splunk-operator |
Customize before deployment
To customize the Splunk Operator before deploying, download a copy of the installation YAML, update the settings from the table above, and apply the customized file.
- Download the installation YAML:
CODE
wget -O splunk-operator-cluster.yaml https://github.com/splunk/splunk-operator/releases/download/<version>/splunk-operator-cluster.yaml - Open the file in your editor and update the settings from the table above.
- Apply the customized YAML:
CODE
kubectl apply -f splunk-operator-cluster.yaml --server-side
Customize after deployment
To customize the Splunk Operator after deploying, edit the splunk-operator-controller-manager deployment to update settings:
CODE
kubectl edit deployment splunk-operator-controller-manager -n splunk-operator