Repository navigation
Splunk Operator: compatibility with OpenShift version 4.20 #1717
Description
Please select the type of request
Enhancement
Tell us more
Describe the request
We would like for Splunk Operator to be compatible with 4.20 version of OpenShift.
Expected behavior
Splunk operator installed via OLM supports 4.20 version of OpenShift and has appropriate value set in ClusterServiceVersion. Current 3.0.0 version (https://github.com/redhat-openshift-ecosystem/certified-operators/blob/main/operators/splunk-operator/3.0.0/manifests/splunk-operator.clusterserviceversion.yaml) has:
olm.properties: '[{"type": "olm.maxOpenShiftVersion", "value": "4.19"}]'
Splunk setup on K8S
We use OpenShift OLM to install the operator.
Reproduction/Testing steps
- Install OpenShift 4.19.
- Install SplunkOperator 3.0.0 via OLM.
- In ClusterSettings in OpenShift console you get error:
This cluster should not be updated to 4.20. You can continue to update to patch releases in 4.19.
Cluster operator operator-lifecycle-manager should not be upgraded between minor versions: ClusterServiceVersions blocking minor version upgrades to 4.20.0 or higher:
maximum supported OCP version for openshift-operators/splunk-operator.v3.0.0 is 4.19
K8s environment
OpenShift 4.19
Thank you,
Michał
Activity
pstefka commentedon Oct 5, 2026
This issue is wrongly marked as enhancement. It is a bug. Plus the same issue is prevalent in the 3.1.0 release as well.
Why is it an issue and not an enhancement?
From splunk operator release notes:
Splunk Operator 3.1.0 supports Kubernetes 1.25 through 1.34 *
Splunk Operator 3.0.0 supports Kubernetes 1.25 through 1.34 *
Where:
K8s 1.33 = Openshift 4.20
K8s 1.34 = Openshift 4.21
Both 3.0, and 3.1 CSV should be changed either to 4.21, or at least 4.20.
As the operator has been tested on these k8s versions, the PR should be rather simple.
pstefka commentedon Oct 8, 2026
@vivekr-splunk can you please remove the enhancement label as per my analysis above?