-
Notifications
You must be signed in to change notification settings - Fork 115
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Splunk Operator: Error SearchHeadcluster and IndexerCluster #1331
Comments
Deploy Splunk Operator chartDisable if the Splunk Operator is already deployedsplunk-operator: sva:
indexerCluster: extraEnv: livenessInitialDelaySeconds: 300 etcVolumeStorageConfig: varVolumeStorageConfig: clusterManager: livenessInitialDelaySeconds: 300 varVolumeStorageConfig: searchHeadCluster: serviceTemplate: extraEnv: livenessInitialDelaySeconds: 300 etcVolumeStorageConfig: varVolumeStorageConfig: this is my code |
@Zeroxcharisma can you try upgrading SOK to 2.6.1. |
Hello @Zeroxcharisma, Did you have a chance to upgrade SOK to the latest available version and validate if this still persists? |
Please select the type of request
Bug
Tell us more
Describe the request
I am trying to deploy the c3 architecture of splunk on my kubernetes cluster using helm chart , and I found a small test that you got under kuttl file , containing the c3 deployment , the result is failing with errors on the searchhead and the indexercluster .
Expected behavior
see my pods up and running with the searchhead cluster , indexercluster and clustermanager
Splunk setup on K8S
using helm chart that you got and this two images :
-splunk-operator.image.repository=docker.io/splunk/splunk:9.2
-splunk-operator.splunkOperator.image.repository=docker.io/splunk/splunk-operator:2.5.2
Reproduction/Testing steps
as you can see here pods are running
but this is not :
and I don't have any pod for indexercluster :
K8s environment
The text was updated successfully, but these errors were encountered: