CSPL-3673: Update install docs with arguments

docs/Install.md

@@ -18,7 +18,7 @@ By installing `splunk-operator-cluster.yaml` Operator will watch all the namespa
 
 ```
 wget -O splunk-operator-cluster.yaml https://github.com/splunk/splunk-operator/releases/download/2.7.1/splunk-operator-cluster.yaml
-kubectl apply -f splunk-operator-cluster.yaml
+kubectl apply -f splunk-operator-cluster.yaml --server-side
 ```
 
 ## Install operator to watch multiple namespaces
@@ -48,7 +48,7 @@ In order to install operator with restrictive permission to watch only single na
 
 ```
 wget -O splunk-operator-namespace.yaml https://github.com/splunk/splunk-operator/releases/download/2.7.1/splunk-operator-namespace.yaml
-kubectl apply -f splunk-operator-namespace.yaml
+kubectl apply -f splunk-operator-namespace.yaml --server-side
 ```
 
 ## Private Registries

docs/README.md

@@ -113,14 +113,16 @@ For production environments, we are requiring the use of Splunk SmartStore. As a
 
 A Kubernetes cluster administrator can install and start the Splunk Operator for specific namespace by running:
 ```
-kubectl apply -f https://github.com/splunk/splunk-operator/releases/download/2.7.1/splunk-operator-namespace.yaml --server-side  --force-conflicts
+kubectl apply -f https://github.com/splunk/splunk-operator/releases/download/2.7.1/splunk-operator-namespace.yaml --server-side
 ```
 
 A Kubernetes cluster administrator can install and start the Splunk Operator for cluster-wide by running:
 ```
-kubectl apply -f https://github.com/splunk/splunk-operator/releases/download/2.7.1/splunk-operator-cluster.yaml --server-side  --force-conflicts
+kubectl apply -f https://github.com/splunk/splunk-operator/releases/download/2.7.1/splunk-operator-cluster.yaml --server-side
 ```
 
+The reason for appending `--server-side` to the apply command is that some of the CRDs are getting too long according to the CRD standards. There are no real implications caused by this.
+
 The [Advanced Installation Instructions](Install.md) page offers guidance for advanced configurations, including the use of private image registries, installation at cluster scope, and installing the Splunk Operator as a user who is not a Kubernetes administrator. Users of Red Hat OpenShift should review the [Red Hat OpenShift](OpenShift.md) page.
 
 *Note: We recommended that the Splunk Enterprise Docker image is copied to a private registry, or directly onto your Kubernetes workers before creating large Splunk Enterprise deployments. See the [Required Images Documentation](Images.md) page, and the [Advanced Installation Instructions](Install.md) page for guidance on working with copies of the Docker images.*

docs/SplunkOperatorUpgrade.md

@@ -33,7 +33,7 @@ wget -O splunk-operator-namespace.yaml https://github.com/splunk/splunk-operator
 ​
 3. Upgrade the Splunk Operator.​
 ```
-kubectl apply -f splunk-operator-namespace.yaml --server-side  --force-conflicts
+kubectl apply -f splunk-operator-namespace.yaml --server-side
 ```
 ​
 After applying the yaml, a new operator pod will be created and the existing operator pod will be terminated. Example: