Multiple clusters failing the UI if one has a bad config

[tontondematt]

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)

Hi I have installed kafka-ui v1.4.1 and I am trying to create multiple clusters.
If one of my cluster has a bad config, for example a bad password both clusters fails and the one that is correctly set up never becomes green.
Is this a known issue ? how can I fix this ?
And yes I can make sure that a password is never wrong and what not ... but passwords can expire i'd like to avoid it crashing because of one bad cluster in my production.

Expected behavior

Kakfa-ui runs and only the cluster with the bad config is not ready

Your installation details

1. v1.4.1
2. helm latest one
3. two cluster configured via configmap
4. Running on eks 1.31

Steps to reproduce

just configure two cluster, one of which has some bad config, bad bootstrap url or password

Screenshots

No response

Logs

No response

Additional context

No response

[github-actions]

Hi tontondematt! 👋

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.

[Haarolean]

a config example to reproduce this, please

[kapybro]

Further user feedback is requested. Please reply within 7 days or we might close the issue.

[tontondematt]

a config example to reproduce this, please

Sure here is my config: cluster1 work when created alone, cluster2 will not work bc of a wrong password, but when creating both clusters together if the second one has a wrong passowrd both are broken (yellow status) and the ui is unusable.

```
kafka:
  clusters:
    - name: cluster1
      bootstrapServers: mybootstapserver:443
      properties:
        security.protocol: SASL_SSL
        sasl.mechanism: OAUTHBEARER
        sasl.jaas.config: org.apache.kafka.common.security.oauthbearer.OAuthBearerLoginModule required  oauth.token.endpoint.uri="https://myoauth2/oauth/token" oauth.client.id="client1" oauth.client.secret="secret1" oauth.ssl.truststore.location="/stores/truststore.jks" oauth.ssl.truststore.password="changeit" oauth.ssl.truststore.type="JKS" oauth.enable.metrics="true";
        sasl.login.callback.handler.class: io.strimzi.kafka.oauth.client.JaasClientOauthLoginCallbackHandler
        ssl.truststore.location: /stores/truststore.jks
        ssl.truststore.password: changeit
        ssl.truststore.type: JKS
        bootstrap.servers: mybootstapserver:443
    - name: cluster2
      bootstrapServers: mybootstapserver:443
      properties:
        security.protocol: SASL_SSL
        sasl.mechanism: OAUTHBEARER
        sasl.jaas.config: org.apache.kafka.common.security.oauthbearer.OAuthBearerLoginModule required  oauth.token.endpoint.uri="https://myoauth2/oauth/token" oauth.client.id="client2" oauth.client.secret="wrongsecret" oauth.ssl.truststore.location="/stores/truststore.jks" oauth.ssl.truststore.password="changeit" oauth.ssl.truststore.type="JKS" oauth.enable.metrics="true";
        sasl.login.callback.handler.class: io.strimzi.kafka.oauth.client.JaasClientOauthLoginCallbackHandler
        ssl.truststore.location: /stores/truststore.jks
        ssl.truststore.password: changeit
        ssl.truststore.type: JKS
        bootstrap.servers: mybootstapserver:443
auth:
  type: OAUTH2
  oauth2:  
    client:
      gardian:
        clientId: UUUUU
        clientSecret: XXXXX 
        scope: openid, isMemberOf
        client-name: myssoo
        provider: myssoo
        authorization-grant-type: authorization_code
        redirect-uri: https://myurl/login/oauth2/code/gardian
        authorization-uri: https://mysso/oauth2/multiauth/authorize?acr_values=GRP
        issuer-uri:  https://mysso/oauth2/multiauth
        user-name-attribute: sub
        custom-params:
          type: oauth
          roles-field: isMemberOf
          logoutUrl: https://myrul/login   
```

[kapybro]

Thanks for the additional feedback! We'll get back to your issue soon.

[tontondematt]

Were you guys able to reproduce ?