Upgrade the Splunk Operator using Helm
Upgrade an existing Splunk Operator deployment using helm upgrade with a values file or the CLI.
If you already installed the Splunk Operator with Helm, use helm upgrade to update your configuration or move to a newer chart version. You can specify new values using a values file or the Helm CLI. To check whether a release exists, run helm list -n <RELEASE_NAMESPACE>. If no release exists, install the Splunk Operator first.
For more information on configurable values, see the splunk/splunk-operator values in the Splunk Operator GitHub repository.
To upgrade with manifest files instead, see Upgrade the Splunk Operator using manifest files.
- Before you upgrade, review the Splunk Operator change log, which notes Splunk Enterprise Docker image compatibility for each release.
- If the Docker image changes, review the Upgrade Readme and How to upgrade Splunk Enterprise for compatibility and upgrade guidance.
- If you use forwarders, verify version compatibility in Compatibility between forwarders and Splunk Enterprise indexers.
Use a new_values.yaml file to override values:
helm upgrade -f new_values.yaml <RELEASE_NAME> splunk/splunk-operator -n <RELEASE_NAMESPACE>
Or use the Helm CLI to set new values directly:
helm upgrade --set <KEY>=<VALUE> <RELEASE_NAME> splunk/splunk-operator -n <RELEASE_NAMESPACE>
The following example upgrades the splunk-operator-test release by revoking cluster-wide access:
helm upgrade --set splunkOperator.clusterWideAccess=false splunk-operator-test splunk/splunk-operator -n splunk-operator
Expected output:
NAME: splunk-operator-test
LAST DEPLOYED: Tue Aug 23 12:53:08 2022
NAMESPACE: splunk-operator
STATUS: deployed
REVISION: 2
TEST SUITE: None