Install the Splunk Operator using kubectl

Deploy the Splunk Operator using namespace-scoped or cluster-wide YAML manifest files.

Install the Splunk Operator for Kubernetes using kubectl with namespace-scoped or cluster-wide manifest files. YAML manifest files offer a simple, single-command deployment with no additional tooling. By default, the operator installs in the splunk-operator namespace. To change the default installation namespace, edit the manifest file before applying it.

Note: To run kubectl commands from your local workstation, you must install the Kubernetes CLI (kubectl) on your operating system. See Install Tools.

Install for a specific namespace

Use the namespace-scoped manifest to install the operator with restrictive permissions. This creates a Role and RoleBinding that limit the operator to watching only its deployed namespace.

CODE 
kubectl apply -f https://github.com/splunk/splunk-operator/releases/download/<version>/splunk-operator-namespace.yaml --server-side

Install cluster-wide

Use the cluster-wide manifest to install the operator with permissions to watch all namespaces. This creates a ClusterRole and ClusterRoleBinding.

CODE 
kubectl apply -f https://github.com/splunk/splunk-operator/releases/download/<version>/splunk-operator-cluster.yaml --server-side

Installation notes

Note: The --server-side flag is appended because some of the CRDs exceed the standard CRD size limits. There are no other implications from using this flag.

Verify the Splunk Operator is running

After the Splunk Operator starts, a single pod runs within your current namespace:

CODE 
$ kubectl get pods
NAME                               READY   STATUS    RESTARTS   AGE
splunk-operator-75f5d4d85b-8pshn   1/1     Running   0          5s