K8SSAND-1040 ⁃ Cassandra Reaper shows additional default rack with customized rack name

[mikekuzak]

Bug Report

Describe the bug When changing the dc/rack name in the helm chart the Reaper UI shows also an additional default rack

To Reproduce Steps to reproduce the behavior:

cassandra:
  version: "3.11.10"
  allowMultipleNodesPerWorker: false
  cassandraLibDirVolume:
    storageClass: local-path
    size: 120Gi
  heap:
   size: 6G
   newGenSize: 6G
  resources:
    limits:
      cpu: 4000m
      memory: 10Gi
  datacenters:
  - name: us2
    size: 3
    racks:
    - name: qa
stargate:
  enabled: true
  replicas: 1
  heapMB: 256
  cpuReqMillicores: 200
  cpuLimMillicores: 2000
  ingress:
    enabled: false

reaper:
  autoschedule: true
  enabled: true
  ingress:
    enabled: false

1. Get to the Reaper Repair website

Expected behavior Default rack shouldn't be present

Environment (please complete the following information): Cassandra v3.11.10

• Helm charts version info 3.5.0
• Kubernetes version information: 1.19.6
• Kubernetes cluster kind: helm chart v.1.3.1

It has something to do with Stargate. The pod has a rack env. variable which is still 'default'. When I change it the reaper moves the rack into the custom cluster

Or with assigned racks:

┆Issue is synchronized with this Jira Task by Unito ┆friendlyId: K8SSAND-1040 ┆priority: Medium

[mikekuzak]

https://github.com/k8ssandra/k8ssandra/blob/main/charts/k8ssandra/templates/stargate/stargate.yaml#L107

[adejanovski]

Stargate is definitely not playing well with the Reaper UI. My take on this is that Stargate nodes shouldn't show up as the other nodes in the UI, with just an indication of the number of Stargate nodes on the left, like we do for all nodes:

Nodes: 3
Stargate nodes: 1
...

We can identify Stargate nodes from their special Gossip state X10, which should make this fairly easy.

[jdonenine]

Sounds good @adejanovski thanks for the context.

I went ahead and created an issue over in Reaper to look at adding the UI changes: https://github.com/thelastpickle/cassandra-reaper/issues/1145.

I will leave this issue here in K8ssandra open just to give us something to track the upstream change and integrate it later here.