Number of Messages in topic shows 'N/A' in version 1.4.2

[eichstep]

Issue submitter TODO list

• I've looked up my issue in FAQ
• I've searched for an already existing issues here
• I've tried running main-labeled docker image and the issue still persists there
• I'm running a supported version of the application which is listed here

Describe the bug (actual behavior)

When heading to the 'topics' view of a cluster, all topics are shown as expected. The column 'Number of messages' shows 'N/A' for every single line in that list.
This behavior was different on the previously used version 1.3.0 Downgrading shows the proper overview again.

Additionally, when heading to a single topic, the 'Message Count' shows the correct number. Therefore, this cannot be an access issue of the kafka-account, as the access works as expected.

Expected behavior

The list shows the correct number of messages for all entries in the list.

Your installation details

kafbat version v1.4.2, commit dfa5a7e
Helm chart version 1.5.3

Helm values (deployed through argocd valuesObject):

env:
  - name: AUTH_TYPE
    value: LOGIN_FORM
  - name: SPRING_SECURITY_USER_NAME
    value: admin
  - name: KAFKA_CLUSTERS_0_NAME
    value: <<redacted>>
  - name: KAFKA_CLUSTERS_0_BOOTSTRAPSERVERS
    value: <<redacted>>
  - name: KAFKA_CLUSTERS_0_PROPERTIES_SECURITY_PROTOCOL
    value: SASL_SSL
  - name: KAFKA_CLUSTERS_0_PROPERTIES_SASL_MECHANISM
    value: PLAIN
existingSecret: kafka-ui-credentials
ingress:
  enabled: true
  host: <<redacted>>
  ingressClassName: nginx-internal
resources:
  limits:
    cpu: 500m
    memory: 1024Mi
  requests:
    cpu: 200m
    memory: 512Mi

Kafka cluster running as Confluent managed cluster. User in kafka has DeveloperRead for all topics as well as all consumer groups on the cluster

Steps to reproduce

• Deploy confluent cluster, have service account added with DeveloperRead to all topics and all consumer groups.
• Add API key to service account
• Deploy helm-chart with SPRING_SECURITY_USER_PASSWORD and KAFKA_CLUSTERS_0_PROPERTIES_SASL_JAAS_CONFIG set up in the pre-existing secret
• Go to webinterface, log into admin account and head to Topic view

Screenshots

Logs

No response

Additional context

No response

[github-actions]

Hi eichstep! 👋

Welcome, and thank you for opening your first issue in the repo!

Please wait for triaging by our maintainers.

As development is carried out in our spare time, you can support us by sponsoring our activities or even funding the development of specific issues.
Sponsorship link

If you plan to raise a PR for this issue, please take a look at our contributing guide.

[DDDFiish]

i got the same issue