Backport main to develop for Splunk Operator Release 2.8.1 (#1542) (#1543)

*  release 2.8.1 chnages - backported

---------

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Co-authored-by: Patryk Wasielewski <[email protected]>
Co-authored-by: patrykw-splunk <[email protected]>

Author: 3 people

.env

@@ -8,4 +8,4 @@ EKSCTL_VERSION=v0.191.0
 EKS_CLUSTER_K8_VERSION=1.31
 EKS_INSTANCE_TYPE=m5.2xlarge
 EKS_INSTANCE_TYPE_ARM64=c6g.4xlarge
-SPLUNK_ENTERPRISE_RELEASE_IMAGE=splunk/splunk:9.4.1
+SPLUNK_ENTERPRISE_RELEASE_IMAGE=splunk/splunk:9.4.3

Dockerfile

@@ -73,7 +73,7 @@ RUN if grep -q 'Ubuntu' /etc/os-release; then \
 LABEL name="splunk" \
       maintainer="[email protected]" \
       vendor="splunk" \
-      version="2.8.0" \
+      version="2.8.1" \
       release="1" \
       summary="Simplify the Deployment & Management of Splunk Products on Kubernetes" \
       description="The Splunk Operator for Kubernetes (SOK) makes it easy for Splunk Administrators to deploy and operate Enterprise deployments in a Kubernetes infrastructure. Packaged as a container, it uses the operator pattern to manage Splunk-specific custom resources, following best practices to manage all the underlying Kubernetes objects for you."

Makefile

@@ -8,7 +8,7 @@ ${ENVIRONMENT}:
 # To re-generate a bundle for another specific version without changing the standard setup, you can:
 # - use the VERSION as arg of the bundle target (e.g make bundle VERSION=0.0.2)
 # - use environment variables to overwrite this value (e.g export VERSION=0.0.2)
-VERSION ?= 2.8.0
+VERSION ?= 2.8.1
 
 # SPLUNK_ENTERPRISE_IMAGE defines the splunk docker tag that is used as default image.
 SPLUNK_ENTERPRISE_IMAGE ?= "docker.io/splunk/splunk"

bundle/manifests/splunk-operator.clusterserviceversion.yaml

@@ -111,16 +111,16 @@ metadata:
     capabilities: Seamless Upgrades
     categories: Big Data, Logging & Tracing, Monitoring, Security, AI/Machine Learning
     containerImage: splunk/splunk-operator@sha256:c4e0d314622699496f675760aad314520d050a66627fdf33e1e21fa28ca85d50
-    createdAt: "2025-04-25T05:04:32Z"
+    createdAt: "2025-07-16T09:03:58Z"
     description: The Splunk Operator for Kubernetes enables you to quickly and easily
       deploy Splunk Enterprise on your choice of private or public cloud provider.
       The Operator simplifies scaling and management of Splunk Enterprise by automating
       administrative workflows using Kubernetes best practices.
-    olm.properties: '[{"type": "olm.maxOpenShiftVersion", "value": "4.15"}]'
+    olm.properties: '[{"type": "olm.maxOpenShiftVersion", "value": "4.19"}]'
     operators.operatorframework.io/builder: operator-sdk-v1.31.0
     operators.operatorframework.io/project_layout: go.kubebuilder.io/v3
     repository: https://github.com/splunk/splunk-operator
-  name: splunk-operator.v2.8.0
+  name: splunk-operator.v2.8.1
   namespace: placeholder
 spec:
   apiservicedefinitions: {}
@@ -393,14 +393,14 @@ spec:
                     fieldRef:
                       fieldPath: metadata.annotations['olm.targetNamespaces']
                 - name: RELATED_IMAGE_SPLUNK_ENTERPRISE
-                  value: docker.io/splunk/splunk:9.4.1
+                  value: docker.io/splunk/splunk:9.4.3
                 - name: OPERATOR_NAME
                   value: splunk-operator
                 - name: POD_NAME
                   valueFrom:
                     fieldRef:
                       fieldPath: metadata.name
-                image: docker.io/splunk/splunk-operator:2.8.0
+                image: docker.io/splunk/splunk-operator:2.8.1
                 imagePullPolicy: Always
                 livenessProbe:
                   httpGet:
@@ -513,7 +513,7 @@ spec:
     name: Splunk Inc.
     url: www.splunk.com
   relatedImages:
-  - image: docker.io/splunk/splunk:9.4.1
+  - image: docker.io/splunk/splunk:9.4.3
     name: splunk-enterprise
-  replaces: splunk-operator.v2.7.1
-  version: 2.8.0
+  replaces: splunk-operator.v2.8.0
+  version: 2.8.1

config/manager/kustomization.yaml

@@ -17,4 +17,4 @@ kind: Kustomization
 images:
 - name: controller
   newName: docker.io/splunk/splunk-operator
-  newTag: 2.8.0
+  newTag: 2.8.1

config/manifests/bases/splunk-operator.clusterserviceversion.yaml

@@ -10,9 +10,9 @@ metadata:
       deploy Splunk Enterprise on your choice of private or public cloud provider.
       The Operator simplifies scaling and management of Splunk Enterprise by automating
       administrative workflows using Kubernetes best practices.
-    olm.properties: '[{"type": "olm.maxOpenShiftVersion", "value": "4.15"}]'
+    olm.properties: '[{"type": "olm.maxOpenShiftVersion", "value": "4.19"}]'
     repository: https://github.com/splunk/splunk-operator
-  name: splunk-operator.v2.8.0
+  name: splunk-operator.v2.8.1
   namespace: placeholder
 spec:
   apiservicedefinitions: {}
@@ -119,5 +119,5 @@ spec:
   provider:
     name: Splunk Inc.
     url: www.splunk.com
-  replaces: splunk-operator.v2.7.1
-  version: 2.8.0
+  replaces: splunk-operator.v2.8.0
+  version: 2.8.1

docs/AppFramework.md

@@ -680,7 +680,7 @@ spec:
       serviceAccountName: splunk-operator
       containers:
       - name: splunk-operator
-        image: "docker.io/splunk/splunk-operator:2.8.0"
+        image: "docker.io/splunk/splunk-operator:2.8.1"
         volumeMounts:
         - mountPath: /opt/splunk/appframework/
           name: app-staging

docs/ChangeLog.md

@@ -1,5 +1,23 @@
 # Splunk Operator for Kubernetes Change Log
 
+## 2.8.1 (2025-07-16)
+
+* This is the 2.8.1 release. The Splunk Operator for Kubernetes is a supported platform for deploying Splunk Enterprise with the prerequisites and constraints laid out [here](https://github.com/splunk/splunk-operator/blob/main/docs/README.md#prerequisites-for-the-splunk-operator)
+
+* Update `olm.maxOpenShiftVersion` version in operator's bundle
+
+### Supported Splunk Version
+
+>| Splunk Version|
+>| --- |
+>| 9.4.3 |
+
+### Supported Kubernetes Version
+
+>| Kubernetes Version|
+>| --- |
+>| 1.27+ |
+
 ## 2.8.0 (2025-04-25)
 
 * This is the 2.8.0 release. The Splunk Operator for Kubernetes is a supported platform for deploying Splunk Enterprise with the prerequisites and constraints laid out [here](https://github.com/splunk/splunk-operator/blob/main/docs/README.md#prerequisites-for-the-splunk-operator)

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-cluster.yaml https://github.com/splunk/splunk-operator/releases/download/2.8.0/splunk-operator-cluster.yaml
+wget -O splunk-operator-cluster.yaml https://github.com/splunk/splunk-operator/releases/download/2.8.1/splunk-operator-cluster.yaml
 ```
 
 ## Default Installation
@@ -17,7 +17,7 @@ Based on the file used Splunk Operator can be installed cluster-wide or namespac
 By installing `splunk-operator-cluster.yaml` Operator will watch all the namespaces of your cluster for splunk enterprise custom resources
 
 ```
-wget -O splunk-operator-cluster.yaml https://github.com/splunk/splunk-operator/releases/download/2.8.0/splunk-operator-cluster.yaml
+wget -O splunk-operator-cluster.yaml https://github.com/splunk/splunk-operator/releases/download/2.8.1/splunk-operator-cluster.yaml
 kubectl apply -f splunk-operator-cluster.yaml --server-side
 ```
 
@@ -44,10 +44,10 @@ If Splunk Operator is installed clusterwide and user wants to manage multiple na
 
 ## Install operator to watch single namespace with restrictive permission
 
-In order to install operator with restrictive permission to watch only single namespace use [splunk-operator-namespace.yaml](https://github.com/splunk/splunk-operator/releases/download/2.8.0/splunk-operator-namespace.yaml). This will create Role and Role-Binding to only watch single namespace. By default operator will be installed in `splunk-operator` namespace, user can edit the file to change the namespace.
+In order to install operator with restrictive permission to watch only single namespace use [splunk-operator-namespace.yaml](https://github.com/splunk/splunk-operator/releases/download/2.8.1/splunk-operator-namespace.yaml). This will create Role and Role-Binding to only watch single namespace. By default operator will be installed in `splunk-operator` namespace, user can edit the file to change the namespace.
 
 ```
-wget -O splunk-operator-namespace.yaml https://github.com/splunk/splunk-operator/releases/download/2.8.0/splunk-operator-namespace.yaml
+wget -O splunk-operator-namespace.yaml https://github.com/splunk/splunk-operator/releases/download/2.8.1/splunk-operator-namespace.yaml
 kubectl apply -f splunk-operator-namespace.yaml --server-side
 ```
 
@@ -86,14 +86,14 @@ As part of enhancing security and reducing the attack surface of the Splunk Oper
 
 1. **Image Tag**:
    - The distroless image can be identified by the `-distroless` suffix in its tag.
-   - Example: `splunk/splunk-operator:2.8.0-distroless`
+   - Example: `splunk/splunk-operator:2.8.1-distroless`
 
 2. **Modifying the Deployment**:
    - To use the distroless image, update the `manager` container image in the `splunk-operator-controller-manager` deployment as follows:
 
    ```yaml
    # Replace this with the distroless image name
-   image: splunk/splunk-operator:2.8.0-distroless
+   image: splunk/splunk-operator:2.8.1-distroless
    ```
 
 3. **Private Registry**:
@@ -130,7 +130,7 @@ Since distroless images do not contain a shell, debugging may require additional
        spec:
          containers:
            - name: manager
-             image: splunk/splunk-operator:2.8.0-distroless
+             image: splunk/splunk-operator:2.8.1-distroless
              env:
                - name: WATCH_NAMESPACE
                  value: ""

docs/README.md

@@ -113,12 +113,12 @@ 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.8.0/splunk-operator-namespace.yaml --server-side
+kubectl apply -f https://github.com/splunk/splunk-operator/releases/download/2.8.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.8.0/splunk-operator-cluster.yaml --server-side
+kubectl apply -f https://github.com/splunk/splunk-operator/releases/download/2.8.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.