splunk / splunk-operator

Splunk Operator for Kubernetes
Other
206 stars 114 forks source link

Splunk Operator: helm chart splunk/splunk-enterprise - indexercluster - clusterManagerRef does not work #1102

Open gjanders opened 1 year ago

gjanders commented 1 year ago

Please select the type of request

Bug

Tell us more

Describe the request In the helm chart for an indexerCluster I have a clusterManagerRef:

indexerCluster:
  enabled: true
<cut>
  clusterManagerRef:
    name: mobiles-cm

However this does not become part of the indexercluster CRD when the helm chart is installed and therefore the indexer cluster of a multisite indexer cluster refuses to start

Expected behavior If I now run: kubectl edit indexercluster

Under spec I expect:

  clusterManagerRef:
    name: mobiles-cm

However this does not appear and therefore the indexer cluster stays in "pending" status

Splunk setup on K8S Multi-site indexer cluster using helm charts, I'm attempting to configure 1 site of the indexer cluster (either site fails)

Reproduction/Testing steps As per details

K8s environment Tested on k8s 1.2.21, Splunk operator 2.2.0 and the current Helm chart as of 6th March 2023

Proposed changes(optional) Allow clusterManagerRef, otherwise I have to complete a manual edit after the helm install runs to get the indexer cluster to run!

K8s collector data(optional) Let me know if you need this...

Additional context(optional) Happy for questions...or a discussion on slack

vivekr-splunk commented 1 year ago

@gjanders thanks for raising this issue. I am looking into this issue now. will update you once I am done with my investigation.

vivekr-splunk commented 1 year ago

@gjanders can you give provide the chart values you setup for multisite ? are you usingsva m4 ?

gjanders commented 1 year ago
splunk-operator:
  enabled: false

indexerCluster:
  enabled: true
  name: mobiles-idxc-site2
  #replicaCount: 20
  replicaCount: 2
  etcVolumeStorageConfig:
    ephemeralStorage: false
    storageCapacity: 5Gi
  # storageClassName: gp2

  varVolumeStorageConfig:
    ephemeralStorage: false
    storageCapacity: 1000Gi
  # storageClassName: gp2
  resources:
     requests:
       memory: "40Gi"
       cpu: "20"
     limits:
       memory: "62Gi"
       cpu: "32"
  clusterManagerRef:
    name: mobiles-cm
  defaults:
    splunk:
      multisite_master: splunk-mobiles-cm-cluster-manager-service
      site: site2
  affinity:
    ## Example: schedule Splunk instance pod on a node in zone-1a
    nodeAffinity:
      requiredDuringSchedulingIgnoredDuringExecution:
        nodeSelectorTerms:
        - matchExpressions:
          - key: mobile-iot-site
            operator: In
            values:
            - "2"