Description
Issue submitter TODO list
- I've searched for an already existing issues here
- I'm running a supported version of the application which is listed here and the feature is not present there
Is your proposal related to a problem?
No response
Describe the feature you're interested in
Prerequisites
Kafka UI users can have multiple Kafka clusters.
Currently, navigation between clusters have some inconveniences. For example, It's impossible to navigate to clusters from the Dashboard
I, as a Kafka UI user, want to be able to go to the Brokers page of the cluster, which name I clicked on the Dashboard page
To do
Implement a redirection mechanism from the Dashboard page to the Brokers page of a cluster, whose name was clicked by the user.
Acceptance criteria
Scenario 1: Successful redirection to the Brokers page of the selected cluster.
Given
- A Kafka UI user is on the Dashboard page.
- The Dashboard page displays a list or overview of multiple Kafka clusters, each with a clickable name or identifier.
When
The user clicks on the name (or equivalent clickable identifier) of a specific Kafka cluster displayed on the Dashboard.
Then
- The user MUST be redirected to the Brokers page specifically for the clicked cluster.
- The URL in the browser MUST update to reflect the Brokers page of that particular cluster.
- The Brokers page MUST display accurate and up-to-date information pertaining to the brokers of the selected cluster.
- All other navigation elements (e.g., sidebar menus) MUST reflect that the user is now viewing the selected cluster.
Scenario 2: Handling of invalid or non-existent cluster names (if applicable).
Given
- A Kafka UI user is on the Dashboard page.
- Due to data inconsistencies or a rare edge case, a cluster name displayed on the Dashboard might point to a non-existent or inaccessible cluster (unlikely for a clickable element, but good to consider for robustness).
When
The user clicks on the name of a cluster that is determined to be invalid or inaccessible upon redirection attempt.
Then
- The system must display an appropriate error message (e.g., "Cluster not found" or "Unable to access cluster information").
- The user must not be stuck on a blank or broken page, and ideally remains on the Dashboard or is redirected to a suitable error page.
Describe alternatives you've considered
No response
Version you're running
1.2.0
Additional context
No response