Monitoring Console: Creation of the monitoring console with the appframework scope: cluster results in the operator crashing

[gjanders]

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

• Useful information about the K8S environment being used. Eg. version of K8s, kind of K8s cluster etc..

Proposed changes(optional)

• Proposed change, if any.

  appRepo:
    appSources:
    - location: adminApps/
      name: adminApps
    appsRepoPollIntervalSeconds: 60
    defaults:
      scope: cluster

To:

    defaults:
      scope: local

K8s collector data(optional)

• Please provide data collected from the [K8s collectors](https://github.com/splunk/splunk-
  -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:

• The log file from the last operator pod startup failure
• The MC yaml config that fails
• The MC yaml config that works

operator-pod-logs.txt
mc-success.yaml.txt
mc-failure.yaml.txt

[vivekr-splunk]

@gjanders thank you for raising this issue. we will look into this issue , if your proposed change works we will incorporate and update it in the future release.