CSPL-929 - Upgrade Operator version to 1.0.0-RC

deploy/olm-catalog/splunk/1.0.0/enterprise.splunk.com_clustermasters_crd.yaml → deploy/olm-catalog/splunk/1.0.0-RC/enterprise.splunk.com_clustermasters_crd.yaml

@@ -1098,12 +1098,6 @@ spec:
                     type: object
                   type: array
               type: object
-            sparkImage:
-              description: Image to use for Spark pod containers (overrides RELATED_IMAGE_SPLUNK_SPARK
-                environment variables). Also used on cluster master for init container
-                to setup the soft links from ../master-apps/splunk-operator/local/
-                to /mnt/splunk-operator/local/
-              type: string
             tolerations:
               description: Pod's tolerations for Kubernetes node's taint
               items:

deploy/olm-catalog/splunk/1.0.0/enterprise.splunk.com_searchheadclusters_crd.yaml → deploy/olm-catalog/splunk/1.0.0-RC/enterprise.splunk.com_searchheadclusters_crd.yaml

@@ -1022,48 +1022,6 @@ spec:
                       type: object
                   type: object
               type: object
-            sparkImage:
-              description: Image to use for Spark pod containers (overrides RELATED_IMAGE_SPLUNK_SPARK
-                environment variables)
-              type: string
-            sparkRef:
-              description: SparkRef refers to a Spark cluster managed by the operator
-                within Kubernetes When defined, Data Fabric Search (DFS) will be enabled
-                and configured to use the Spark cluster.
-              properties:
-                apiVersion:
-                  description: API version of the referent.
-                  type: string
-                fieldPath:
-                  description: 'If referring to a piece of an object instead of an
-                    entire object, this string should contain a valid JSON/Go field
-                    access statement, such as desiredState.manifest.containers[2].
-                    For example, if the object reference is to a container within
-                    a pod, this would take on a value like: "spec.containers{name}"
-                    (where "name" refers to the name of the container that triggered
-                    the event) or if no container name is specified "spec.containers[2]"
-                    (container with index 2 in this pod). This syntax is chosen only
-                    to have some well-defined way of referencing a part of an object.
-                    TODO: this design is not final and this field is subject to change
-                    in the future.'
-                  type: string
-                kind:
-                  description: 'Kind of the referent. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds'
-                  type: string
-                name:
-                  description: 'Name of the referent. More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/names/#names'
-                  type: string
-                namespace:
-                  description: 'Namespace of the referent. More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/namespaces/'
-                  type: string
-                resourceVersion:
-                  description: 'Specific resourceVersion to which this reference is
-                    made, if any. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#concurrency-control-and-consistency'
-                  type: string
-                uid:
-                  description: 'UID of the referent. More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/names/#uids'
-                  type: string
-              type: object
             tolerations:
               description: Pod's tolerations for Kubernetes node's taint
               items:

deploy/olm-catalog/splunk/1.0.0/enterprise.splunk.com_standalones_crd.yaml → deploy/olm-catalog/splunk/1.0.0-RC/enterprise.splunk.com_standalones_crd.yaml

@@ -1119,48 +1119,6 @@ spec:
                     type: object
                   type: array
               type: object
-            sparkImage:
-              description: Image to use for Spark pod containers (overrides RELATED_IMAGE_SPLUNK_SPARK
-                environment variables)
-              type: string
-            sparkRef:
-              description: SparkRef refers to a Spark cluster managed by the operator
-                within Kubernetes When defined, Data Fabric Search (DFS) will be enabled
-                and configured to use the Spark cluster.
-              properties:
-                apiVersion:
-                  description: API version of the referent.
-                  type: string
-                fieldPath:
-                  description: 'If referring to a piece of an object instead of an
-                    entire object, this string should contain a valid JSON/Go field
-                    access statement, such as desiredState.manifest.containers[2].
-                    For example, if the object reference is to a container within
-                    a pod, this would take on a value like: "spec.containers{name}"
-                    (where "name" refers to the name of the container that triggered
-                    the event) or if no container name is specified "spec.containers[2]"
-                    (container with index 2 in this pod). This syntax is chosen only
-                    to have some well-defined way of referencing a part of an object.
-                    TODO: this design is not final and this field is subject to change
-                    in the future.'
-                  type: string
-                kind:
-                  description: 'Kind of the referent. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds'
-                  type: string
-                name:
-                  description: 'Name of the referent. More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/names/#names'
-                  type: string
-                namespace:
-                  description: 'Namespace of the referent. More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/namespaces/'
-                  type: string
-                resourceVersion:
-                  description: 'Specific resourceVersion to which this reference is
-                    made, if any. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#concurrency-control-and-consistency'
-                  type: string
-                uid:
-                  description: 'UID of the referent. More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/names/#uids'
-                  type: string
-              type: object
             tolerations:
               description: Pod's tolerations for Kubernetes node's taint
               items:

deploy/olm-catalog/splunk/1.0.0/splunk.v1.0.0.clusterserviceversion.yaml → deploy/olm-catalog/splunk/1.0.0-RC/splunk.v1.0.0-RC.clusterserviceversion.yaml

@@ -34,16 +34,6 @@ metadata:
           "replicas": 1
         }
       },
-      {
-        "apiVersion": "enterprise.splunk.com/v1",
-        "kind": "Spark",
-        "metadata": {
-          "name": "example"
-        },
-        "spec": {
-          "replicas": 1
-        }
-      },
       {
         "apiVersion": "enterprise.splunk.com/v1",
         "kind": "Standalone",
@@ -54,7 +44,7 @@ metadata:
         "spec": {}
       }]
     capabilities: Basic Install
-  name: splunk.v1.0.0
+  name: splunk.v1.0.0-RC
   namespace: placeholder
 spec:
   apiservicedefinitions: {}
@@ -132,10 +122,9 @@ spec:
         version: v1
       - kind: Secrets
         version: v1
-      displayName: Spark
-    - description: Spark is the Schema for a Spark cluster
-      kind: Spark
-      name: sparks.enterprise.splunk.com
+    - description: Standalone is the Schema for a Splunk Enterprise standalone instances.
+      kind: Standalone
+      name: standalones.enterprise.splunk.com
       version: v1
       resources:
       - kind: StatefulSets
@@ -151,10 +140,6 @@ spec:
       - kind: Secrets
         version: v1
       displayName: Standalone
-    - description: Standalone is the Schema for a Splunk Enterprise standalone instances.
-      kind: Standalone
-      name: standalones.enterprise.splunk.com
-      version: v1
   description: Placeholder description
   displayName: Splunk
   install:
@@ -185,10 +170,8 @@ spec:
                 - name: OPERATOR_NAME
                   value: splunk-operator
                 - name: RELATED_IMAGE_SPLUNK_ENTERPRISE
-                  value: docker.io/splunk/splunk:8.1.2
-                - name: RELATED_IMAGE_SPLUNK_SPARK
-                  value: docker.io/splunk/spark:0.0.2
-                image: docker.io/splunk/splunk-operator:1.0.0
+                  value: docker.io/splunk/splunk:8.1.3
+                image: docker.io/splunk/splunk-operator:1.0.0-RC
                 imagePullPolicy: IfNotPresent
                 name: splunk-operator
                 resources: {}
@@ -259,4 +242,4 @@ spec:
   maturity: alpha
   provider: {}
   replaces: splunk.v0.0.0
-  version: 1.0.0
+  version: 1.0.0-RC

deploy/operator.yaml

@@ -30,4 +30,4 @@ spec:
         - name: OPERATOR_NAME
           value: "splunk-operator"
         - name: RELATED_IMAGE_SPLUNK_ENTERPRISE
-          value: "docker.io/splunk/splunk:8.1.2"
+          value: "docker.io/splunk/splunk:8.1.3"

docs/ChangeLog.md

@@ -1,5 +1,22 @@
 # Splunk Operator for Kubernetes Change Log
 
+## 1.0.0-RC (2021-03-22)
+* This a release candidate for upcoming GA release.
+
+* This release depends upon changes made concurrently in the Splunk Enterprise container images. You should use the splunk/splunk:8.1.3 image with it
+
+* Changed CRD version from v1beta1 to v1, 1.0.0-RC operator version
+
+* CSPL-826 - Created documentation detailing secure Splunk deployments in Kubernetes.
+
+* CSPL-674 - Removed Spark support
+
+* CSPL-624 - Added Splunk Operator upgrade documentation
+
+* Security enhancements 
+
+* Test automation enhancements
+
 ## 0.2.2 Beta(2021-02-09)
 * This release depends upon changes made concurrently in the Splunk Enterprise container images. You should use the splunk/splunk:8.1.2 image with it, or alternatively any release version 8.1.0 or later
 

docs/Ingress.md

@@ -114,7 +114,7 @@ http://<LoadBalance-External-IP>
 
 #### Multiple Hosts Configuration
 
-If your deployment has multiple hosts such as Search Heads and Cluster Master, use this example to configure Splunk Web access, and HTTP Event Collector port. Follow the steps here [HEC Documentation](https://docs.splunk.com/Documentation/Splunk/8.1.2/Data/UsetheHTTPEventCollector) to learn how to create a HEC token and how to send data using HTTP. 
+If your deployment has multiple hosts such as Search Heads and Cluster Master, use this example to configure Splunk Web access, and HTTP Event Collector port. Follow the steps here [HEC Documentation](https://docs.splunk.com/Documentation/Splunk/latest/Data/UsetheHTTPEventCollector) to learn how to create a HEC token and how to send data using HTTP. 
 
 1. Create a Gateway for multiple hosts.
 

docs/Install.md

@@ -7,7 +7,7 @@
 If you want to customize the installation of the Splunk Operator, download a copy of the installation YAML locally, and open it in your favorite editor.
 
 ```
-wget -O splunk-operator.yaml https://github.com/splunk/splunk-operator/releases/download/0.2.2/splunk-operator-install.yaml
+wget -O splunk-operator.yaml https://github.com/splunk/splunk-operator/releases/download/1.0.0-RC/splunk-operator-install.yaml
 ```
 
 
@@ -18,13 +18,13 @@ Kubernetes only allows administrators to install new `CustomResourceDefinition`
 If you are not an administrator, you can have an administrator create the required objects for you by running:
 
 ```
-kubectl apply -f https://github.com/splunk/splunk-operator/releases/download/0.2.2/splunk-operator-crds.yaml
+kubectl apply -f https://github.com/splunk/splunk-operator/releases/download/1.0.0-RC/splunk-operator-crds.yaml
 ```
 
 Afterwards, you can download and use the yaml file to install the operator within your own namespace:
 
 ```
-wget -O splunk-operator.yaml https://github.com/splunk/splunk-operator/releases/download/0.2.2/splunk-operator-noadmin.yaml
+wget -O splunk-operator.yaml https://github.com/splunk/splunk-operator/releases/download/1.0.0-RC/splunk-operator-noadmin.yaml
 kubectl config set-context --current --namespace=<NAMESPACE>
 kubectl apply -f splunk-operator.yaml
 ```
@@ -35,7 +35,7 @@ kubectl apply -f splunk-operator.yaml
 If you want to configure a single instance of the operator to manage all the namespaces of your cluster, use the alternative cluster scope installation yaml file:
 
 ```
-wget -O splunk-operator.yaml https://github.com/splunk/splunk-operator/releases/download/0.2.2/splunk-operator-cluster.yaml
+wget -O splunk-operator.yaml https://github.com/splunk/splunk-operator/releases/download/1.0.0-RC/splunk-operator-cluster.yaml
 ```
 
 When running at cluster scope, you will need to bind the `splunk:operator:namespace-manager` ClusterRole to the `splunk-operator` ServiceAccount in all namespaces you want it to manage. 

docs/README.md

@@ -57,7 +57,7 @@ information.
 
 A Kubernetes cluster administrator can install and start the Splunk Operator by running:
 ```
-kubectl apply -f https://github.com/splunk/splunk-operator/releases/download/0.2.2/splunk-operator-install.yaml
+kubectl apply -f https://github.com/splunk/splunk-operator/releases/download/1.0.0-RC/splunk-operator-install.yaml
 ```
 
 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.

docs/SplunkOperatorUpgrade.md

@@ -21,7 +21,7 @@ A Splunk Operator for Kubernetes upgrade might include support for a later versi
 1. Download the latest Splunk Operator installation yaml file.
 ​
 ```
-wget -O splunk-operator.yaml https://github.com/splunk/splunk-operator/releases/download/0.2.2/splunk-operator-install.yaml 
+wget -O splunk-operator.yaml https://github.com/splunk/splunk-operator/releases/download/1.0.0-RC/splunk-operator-install.yaml 
 ```
 ​
 2. (Optional) Review the file and update it with your specific customizations used during your install. 

version/version.go

@@ -16,5 +16,5 @@ package version
 
 var (
 	// Version of splunk-operator
-	Version = "1.0.0"
+	Version = "1.0.0-RC"
 )