addressing changes for CSPL-1814 in documentation

Signed-off-by: vivekr-splunk <[email protected]>

Author: vivekr-splunk

docs/AppFramework.md

@@ -67,7 +67,7 @@ spec:
         secretRef: s3-secret
 ```
 
-6. Apply the Custom Resource specification: `kubectl apply -f Standalone.yaml`
+6. Apply the Custom Resource specification: `kubectl apply -n splunk-operator -f Standalone.yaml`
 
 The App Framework detects the Splunk app or add-on archive files available in the App Source locations, and deploys them to the standalone instance path for local use. 
 
@@ -133,7 +133,7 @@ spec:
         secretRef: s3-secret
 ```
 
-6. Apply the Custom Resource specification: `kubectl apply -f ClusterMaster.yaml`
+6. Apply the Custom Resource specification: `kubectl apply -n splunk-operator -f ClusterMaster.yaml`
 
 The App Framework detects the Splunk app or add-on archive files available in the App Source locations, and deploys the apps from the `adminApps` folder to the cluster manager instance for local use. 
 
@@ -208,7 +208,7 @@ spec:
         secretRef: s3-secret
 ```
 
-6. Apply the Custom Resource specification: `kubectl apply -f SearchHeadCluster.yaml`
+6. Apply the Custom Resource specification: `kubectl apply -n splunk-operator -f SearchHeadCluster.yaml`
 
 The App Framework detects the Splunk app or add-on archive files available in the App Source locations, and deploys the apps from the `adminApps`  folder to the Deployer instance for local use. 
 

docs/Examples.md

@@ -54,7 +54,7 @@ The Splunk Operator makes creation of a cluster easy by utilizing a `ClusterMast
 
 #### Cluster Manager
 ```yaml
-cat <<EOF | kubectl apply -f -
+cat <<EOF | kubectl apply -n splunk-operator -f -
 apiVersion: enterprise.splunk.com/v3
 kind: ClusterMaster
 metadata:
@@ -73,7 +73,7 @@ The Splunk Operator also controls the upgrade cycle, and implements the recommen
 This example includes the `monitoringConsoleRef` parameter used to define a monitoring console pod. The monitoring console pod does not need to be running; the name can be predefined and the pod started later. To start the monitoring console pod, see [Monitoring Console](#monitoring-console), or use the example below:
 
 ```yaml
-cat <<EOF | kubectl apply -f -
+cat <<EOF | kubectl apply -n splunk-operator -f -
 apiVersion: enterprise.splunk.com/v3
 kind: MonitoringConsole
 metadata:
@@ -89,7 +89,7 @@ The passwords for the instance are generated automatically. To review the passwo
 
 #### Indexer cluster peers
 ```yaml
-cat <<EOF | kubectl apply -f -
+cat <<EOF | kubectl apply -n splunk-operator -f -
 apiVersion: enterprise.splunk.com/v3
 kind: IndexerCluster
 metadata:
@@ -123,7 +123,7 @@ splunk-operator-7c5599546c-wt4xl            1/1     Running   0          14h
 If you want to add more indexers as cluster peers, update your `IndexerCluster` CR and define the `replicas` parameter:
 
 ```yaml
-cat <<EOF | kubectl apply -f -
+cat <<EOF | kubectl apply -n splunk-operator -f -
 apiVersion: enterprise.splunk.com/v3
 kind: IndexerCluster
 metadata:
@@ -176,7 +176,7 @@ indexercluster.enterprise.splunk.com/example scaled
 You can also create [Horizontal Pod Autoscalers](https://kubernetes.io/docs/tasks/run-application/horizontal-pod-autoscale/) to manage dynamic scaling for you. For example:
 
 ```yaml
-cat <<EOF | kubectl apply -f -
+cat <<EOF | kubectl apply -n splunk-operator -f -
 apiVersion: autoscaling/v1
 kind: HorizontalPodAutoscaler
 metadata:
@@ -202,7 +202,7 @@ idc-example   IndexerCluster/example   16%/50%   5         10        5
 To create a standalone search head that is preconfigured to search your indexer cluster, add the `clusterMasterRef` parameter:
 
 ```yaml
-cat <<EOF | kubectl apply -f -
+cat <<EOF | kubectl apply -n splunk-operator -f -
 apiVersion: enterprise.splunk.com/v3
 kind: Standalone
 metadata:
@@ -235,7 +235,7 @@ splunk-operator-7c5599546c-wt4xl              1/1     Running   0          14h
 Having a separate CR for cluster manager allows you to define parameters differently than the indexers, such as storage capacity and the storage class used by persistent volumes.
 
 ```yaml
-cat <<EOF | kubectl apply -f -
+cat <<EOF | kubectl apply -n splunk-operator -f -
 apiVersion: enterprise.splunk.com/v3
 kind: ClusterMaster
 metadata:
@@ -273,7 +273,7 @@ The Monitoring Console provides detailed topology and performance information ab
 
 
 ```yaml
-cat <<EOF | kubectl apply -f -
+cat <<EOF | kubectl apply -n splunk-operator -f -
 apiVersion: enterprise.splunk.com/v3
 kind: MonitoringConsole
 metadata:
@@ -294,7 +294,7 @@ You can create a search head cluster that is configured to communicate with your
 and adding the `clusterMasterRef` parameter. 
 
 ```yaml
-cat <<EOF | kubectl apply -f -
+cat <<EOF | kubectl apply -n splunk-operator -f -
 apiVersion: enterprise.splunk.com/v3
 kind: SearchHeadCluster
 metadata:
@@ -312,7 +312,7 @@ EOF
 This will automatically create a deployer with 3 search heads clustered together. Search head clusters require a minimum of 3 members. This example includes the `monitoringConsoleRef` parameter and name used to define a monitoring console (MC) pod.  To start the monitoring console pod, see [Monitoring Console](#monitoring-console), or use the example below:
 
 ```yaml
-cat <<EOF | kubectl apply -f -
+cat <<EOF | kubectl apply -n splunk-operator -f -
 apiVersion: enterprise.splunk.com/v3
 kind: MonitoringConsole
 metadata:
@@ -689,7 +689,7 @@ spec:
 While configuring [`Indexer Clusters`](Examples.md#indexer-clusters) to use the `LicenseMaster`, you need to add `licenseMasterRef` only to the `ClusterMaster` spec as follows:
 
 ```yaml
-cat <<EOF | kubectl apply -f -
+cat <<EOF | kubectl apply -n splunk-operator -f -
 apiVersion: enterprise.splunk.com/v3
 kind: ClusterMaster
 metadata:

docs/MultisiteExamples.md

@@ -3,11 +3,12 @@
 This document provides examples to configure a multisite cluster using the splunk-operator.
 
 
-- [Multisite Indexer Clusters in Kubernetes](#multisite-indexer-clusters-in-kubernetes)
-- [Multipart IndexerCluster](#multipart-indexercluster)
-    - [Deploy the cluster-manager](#deploy-the-cluster-manager)
-    - [Deploy the indexer sites](#deploy-the-indexer-sites)
-- [Connecting a search-head cluster to a multisite indexer-cluster](#connecting-a-search-head-cluster-to-a-multisite-indexer-cluster)
+- [Configuring Splunk Enterprise Multisite Deployments](#configuring-splunk-enterprise-multisite-deployments)
+  - [Multisite Indexer Clusters in Kubernetes](#multisite-indexer-clusters-in-kubernetes)
+  - [Multipart IndexerCluster](#multipart-indexercluster)
+      - [Deploy the cluster-manager](#deploy-the-cluster-manager)
+      - [Deploy the indexer sites](#deploy-the-indexer-sites)
+  - [Connecting a search-head cluster to a multisite indexer-cluster](#connecting-a-search-head-cluster-to-a-multisite-indexer-cluster)
 
 Please refer to the [Configuring Splunk Enterprise Deployments Guide](Example.md)
 for more information and examples about deploying the different Splunk resources
@@ -47,7 +48,7 @@ Limitation: all the IndexerCluster resources must be located in the same namespa
 Note: the image version is defined in these resources as this allows to control the upgrade cycle 
 
 ```yaml
-cat <<EOF | kubectl apply -f -
+cat <<EOF | kubectl apply -n splunk-operator -f -
 ---
 apiVersion: enterprise.splunk.com/v3
 kind: ClusterMaster
@@ -86,7 +87,7 @@ EOF
 #### Deploy the indexer sites
 
 ```yaml
-cat <<EOF | kubectl apply -f -
+cat <<EOF | kubectl apply -n splunk-operator -f -
 ---
 apiVersion: enterprise.splunk.com/v3
 kind: IndexerCluster
@@ -134,7 +135,7 @@ Additional ansible default parameters must be set to activate multisite:
 (https://docs.splunk.com/Documentation/Splunk/latest/DistSearch/DeploymultisiteSHC#Integrate_a_search_head_cluster_with_a_multisite_indexer_cluster))
 
 ```yaml
-cat <<EOF | kubectl apply -f -
+cat <<EOF | kubectl apply -n splunk-operator -f -
 ---
 apiVersion: enterprise.splunk.com/v3
 kind: SearchHeadCluster

docs/README.md

@@ -140,7 +140,7 @@ The `Standalone` custom resource is used to create a single instance deployment
 
 
 ```yaml
-cat <<EOF | kubectl apply -f -
+cat <<EOF | kubectl apply -n splunk-operator -f -
 apiVersion: enterprise.splunk.com/v3
 kind: Standalone
 metadata: