You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When creating a monitoring console with a particular configuration, the operator pod goes into a crash loop printing an error. On startup the pod crashes and repeats the error in an infinite loop
If I instead use scope: local on the appframework section, the pod works as expected.
Expected behavior
The operator should not crash with this configuration.
Splunk setup on K8S
5 indexer clusters , all multisite with a CM for each.
1 search head cluster
2 standalone pods
Reproduction/Testing steps
I found that the simple change of :
K8s environment
Useful information about the K8S environment being used. Eg. version of K8s, kind of K8s cluster etc..
Please select the type of request
Bug
Tell us more
Describe the request
When creating a monitoring console with a particular configuration, the operator pod goes into a crash loop printing an error. On startup the pod crashes and repeats the error in an infinite loop
If I instead use scope: local on the appframework section, the pod works as expected.
Expected behavior
The operator should not crash with this configuration.
Splunk setup on K8S
5 indexer clusters , all multisite with a CM for each.
1 search head cluster
2 standalone pods
Reproduction/Testing steps
I found that the simple change of :
K8s environment
Proposed changes(optional)
To:
K8s collector data(optional)
-operator/blob/develop/docs/K8SCollectors.md), if any.
If required I can upload this via a support case.
Additional context(optional)
The issue is easily fixed so not currently an issue, I will include:
operator-pod-logs.txt
mc-success.yaml.txt
mc-failure.yaml.txt
The text was updated successfully, but these errors were encountered: