splunk
diff --git a/‎.env‎
Lines changed: 1 addition & 1 deletion b/‎.env‎
Lines changed: 1 addition & 1 deletion
diff --git a/‎.github/workflows/helm-test-workflow.yml‎
Lines changed: 1 addition & 0 deletions b/‎.github/workflows/helm-test-workflow.yml‎
Lines changed: 1 addition & 0 deletions
diff --git a/‎.github/workflows/nightly-int-test-workflow.yml‎
Lines changed: 1 addition & 1 deletion b/‎.github/workflows/nightly-int-test-workflow.yml‎
Lines changed: 1 addition & 1 deletion
diff --git a/‎bundle/manifests/splunk-operator.clusterserviceversion.yaml‎
Lines changed: 5 additions & 5 deletions b/‎bundle/manifests/splunk-operator.clusterserviceversion.yaml‎
Lines changed: 5 additions & 5 deletions
diff --git a/‎config/manager/kustomization.yaml‎
Lines changed: 1 addition & 1 deletion b/‎config/manager/kustomization.yaml‎
Lines changed: 1 addition & 1 deletion
diff --git a/‎config/manifests/bases/splunk-operator.clusterserviceversion.yaml‎
Lines changed: 3 additions & 3 deletions b/‎config/manifests/bases/splunk-operator.clusterserviceversion.yaml‎
Lines changed: 3 additions & 3 deletions
diff --git a/‎docs/AppFramework.md‎
Lines changed: 33 additions & 33 deletions b/‎docs/AppFramework.md‎
Lines changed: 33 additions & 33 deletions
diff --git a/‎docs/ChangeLog.md‎
Lines changed: 16 additions & 0 deletions b/‎docs/ChangeLog.md‎
Lines changed: 16 additions & 0 deletions
diff --git a/‎docs/Install.md‎
Lines changed: 4 additions & 4 deletions b/‎docs/Install.md‎
Lines changed: 4 additions & 4 deletions
diff --git a/‎docs/README.md‎
Lines changed: 2 additions & 2 deletions b/‎docs/README.md‎
Lines changed: 2 additions & 2 deletions
@@ -6,4 +6,4 @@ KUBECTL_VERSION=v1.29.1
 AZ_CLI_VERSION=2.30.0
 EKSCTL_VERSION=v0.143.0
 EKS_CLUSTER_K8_VERSION=1.27
-SPLUNK_ENTERPRISE_RELEASE_IMAGE=splunk/splunk:9.1.3
+SPLUNK_ENTERPRISE_RELEASE_IMAGE=splunk/splunk:9.1.3
@@ -4,6 +4,7 @@ on:
     branches:
       - develop
       - main
+      - feature**
 jobs:
   build-operator-image:
     runs-on: ubuntu-latest
 
@@ -1,7 +1,7 @@
 name: Nightly Integration Test WorkFlow
 on:
   schedule:
-    - cron: "0 06 * * *"
+    - cron: "0 06 * * 0"
 jobs:
   build-operator-image:
     runs-on: ubuntu-latest
 
@@ -111,7 +111,7 @@ metadata:
     capabilities: Seamless Upgrades
     categories: Big Data, Logging & Tracing, Monitoring, Security, AI/Machine Learning
     containerImage: splunk/splunk-operator@sha256:c4e0d314622699496f675760aad314520d050a66627fdf33e1e21fa28ca85d50
-    createdAt: "2024-01-22T21:05:16Z"
+    createdAt: "2024-02-20T18:45:06Z"
     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
@@ -120,7 +120,7 @@ metadata:
     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.2.1
+  name: splunk-operator.v2.5.1
   namespace: placeholder
 spec:
   apiservicedefinitions: {}
@@ -815,7 +815,7 @@ spec:
                   valueFrom:
                     fieldRef:
                       fieldPath: metadata.name
-                image: docker.io/splunk/splunk-operator:2.5.0
+                image: docker.io/splunk/splunk-operator:2.5.1
                 imagePullPolicy: Always
                 livenessProbe:
                   httpGet:
@@ -929,5 +929,5 @@ spec:
   relatedImages:
   - image: docker.io/splunk/splunk:9.1.3
     name: splunk-enterprise
-  replaces: splunk-operator.v2.2.0
-  version: 2.2.1
+  replaces: splunk-operator.v2.5.0
+  version: 2.5.1
@@ -17,4 +17,4 @@ kind: Kustomization
 images:
 - name: controller
   newName: docker.io/splunk/splunk-operator
-  newTag: 2.5.0
+  newTag: 2.5.1
@@ -12,7 +12,7 @@ metadata:
       administrative workflows using Kubernetes best practices.
     olm.properties: '[{"type": "olm.maxOpenShiftVersion", "value": "4.9"}]'
     repository: https://github.com/splunk/splunk-operator
-  name: splunk-operator.v2.2.1
+  name: splunk-operator.v2.5.1
   namespace: placeholder
 spec:
   apiservicedefinitions: {}
@@ -274,5 +274,5 @@ spec:
   provider:
     name: Splunk Inc.
     url: www.splunk.com
-  replaces: splunk-operator.v2.2.0
-  version: 2.2.1
+  replaces: splunk-operator.v2.5.0
+  version: 2.5.1
@@ -1,5 +1,21 @@
 # Splunk Operator for Kubernetes Change Log
 
+## 2.5.1 (2024-02-20)
+
+CSPL-2532: fix for leader election lost issue (#1281)
+
+### Supported Splunk Version
+>| Splunk Version|
+>| --- |
+>| 9.0.8 |
+>| 9.1.3 |
+
+### Supported Kubernetes Version
+>| Kubernetes Version|
+>| --- |
+>| 1.25+ |
+
+
 ## 2.5.0 (2024-02-05)
 
 CSPL-2155: Support for Level-2 Upgrade Strategy in Splunk Operator
 
@@ -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.5.0/splunk-operator-cluster.yaml
+wget -O splunk-operator-cluster.yaml https://github.com/splunk/splunk-operator/releases/download/2.5.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.5.0/splunk-operator-cluster.yaml
+wget -O splunk-operator-cluster.yaml https://github.com/splunk/splunk-operator/releases/download/2.5.1/splunk-operator-cluster.yaml
 kubectl apply -f splunk-operator-cluster.yaml
 ```
 
@@ -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.5.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.5.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.5.0/splunk-operator-namespace.yaml
+wget -O splunk-operator-namespace.yaml https://github.com/splunk/splunk-operator/releases/download/2.5.1/splunk-operator-namespace.yaml
 kubectl apply -f splunk-operator-namespace.yaml
 ```
 
 
@@ -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.5.0/splunk-operator-namespace.yaml --server-side  --force-conflicts
+kubectl apply -f https://github.com/splunk/splunk-operator/releases/download/2.5.1/splunk-operator-namespace.yaml --server-side  --force-conflicts
 ```
 
 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.5.0/splunk-operator-cluster.yaml --server-side  --force-conflicts
+kubectl apply -f https://github.com/splunk/splunk-operator/releases/download/2.5.1/splunk-operator-cluster.yaml --server-side  --force-conflicts
 ```
 
 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.