We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Bug
Describe the request
[yn@ip-100-65-8-59 /]$ kubectl get pods -n splunk-operator NAME READY STATUS RESTARTS AGE splunk-43105-cluster-manager-0 1/1 Running 0 19m splunk-43105-license-manager-0 1/1 Running 0 30m splunk-c-43105-standalone-0 1/1 Running 0 30m splunk-e-43105-deployer-0 0/1 Running 0 8m15s splunk-e-43105-search-head-0 0/1 Running 0 8m15s splunk-e-43105-search-head-1 0/1 Running 0 8m15s splunk-e-43105-search-head-2 /1 Running 0 8m15s splunk-operator-controller-manager-58b545f67c-8rrhx 2/2 Running 0 31m
and then:
NAME READY STATUS RESTARTS AGE splunk-43105-cluster-manager-0 1/1 Running 0 21m splunk-43105-license-manager-0 1/1 Running 0 32m splunk-c-43105-standalone-0 1/1 Running 0 32m splunk-e-43105-deployer-0 0/1 Running 0 11m splunk-e-43105-search-head-0 1/1 Running 0 11m splunk-e-43105-search-head-1 1/1 Running 0 11m splunk-e-43105-search-head-2 1/1 Running 0 11m splunk-operator-controller-manager-58b545f67c-8rrhx 2/2 Running 0 34m splunk-site3-43105-indexer-0 0/1 Running 0 2m17s splunk-site3-43105-indexer-1 0/1 Running 0 2m17s splunk-site3-43105-indexer-2 0/1 Running 0 2m17s
this is unbelievable, and extremely strange that still, in 2.6.1 there is a dependency check between splunk search-heads and indexers!!!!
Expected behavior Indexers should start without dependency of search-heads!
The text was updated successfully, but these errors were encountered:
it was already reported before #1260, and then there were 2 calls, where i described why logic with dependency is broken for kubernetes deployment.
and now can test 2.6.1 and we still see, that part of platform can't be started just because of problematic logic. old case: 3448046
Sorry, something went wrong.
@yaroslav-nakonechnikov we will get back to you with regard to this issue.
vivekr-splunk
No branches or pull requests
Please select the type of request
Bug
Tell us more
Describe the request
and then:
this is unbelievable, and extremely strange that still, in 2.6.1 there is a dependency check between splunk search-heads and indexers!!!!
Expected behavior
Indexers should start without dependency of search-heads!
The text was updated successfully, but these errors were encountered: