[BUG] v1.5.0 regression: ClusterAuthorizationException from describeLogDirs invalidates AdminClient, breaking Confluent Cloud clusters

[wserr]

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)

Summary

Upgrading from v1.4.2 → v1.5.0 causes Confluent Cloud clusters to become completely inaccessible. The root cause is a combination of two things: StatisticsService always calls describeLogDirs() (unsupported on Confluent Cloud), and v1.5.0 introduced AdminClient invalidation on ClusterAuthorizationException, which was not present in v1.4.2.

Root cause

ScrapedClusterState.scrape() unconditionally calls ac.describeLogDirs(). Confluent Cloud is a managed service and does not support this admin API, returning ClusterAuthorizationException.

In v1.5.0, StatisticsService.getStatistics() added:

.doOnError(e -> adminClientService.invalidate(cluster, e))

And AdminClientServiceImpl.invalidate() kills the AdminClient for any org.apache.kafka.common.errors.* exception — including ClusterAuthorizationException. This makes the entire cluster unreachable.

In v1.4.2 the invalidation did not exist, so the error was logged and the cluster continued to function.

Expected behavior

No response

Your installation details

• Docker compose
• Kafka-UI version 1.5.0
• Confluent cloud environment

Steps to reproduce

1. Configure kafbat-ui against a Confluent Cloud cluster with SASL_SSL / PLAIN
2. Run v1.4.2 → works fine
3. Upgrade to v1.5.0 → cluster immediately shows as offline

Screenshots

No response

Logs

ERROR io.kafbat.ui.service.StatisticsService   : Failed to collect cluster <name> info
org.apache.kafka.common.errors.ClusterAuthorizationException: Cluster authorization failed.
WARN  io.kafbat.ui.service.AdminClientServiceImpl : AdminClient for the cluster <name> is invalidated due to Cluster authorization failed.

Additional context

No response

[github-actions]

Hi wserr! 👋

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.