feat(ui): add multi-cluster user logout

[alokdangre]

Summary

• Visual support for displaying authenticated users per cluster in TopBar.
• Implemented individual cluster logout functionality.
• Added SelfSubjectReview API support for fetching user info.
• Fixed multi-cluster selection state bug in useSelectedClusters hook.
• Improved logout UX to persist view on remaining clusters.

Related Issue

Fixes #4082

Changes

• Updated TopBar.tsx component, clusterApi

Steps to Test

1. select multiple clusters to view
2. click on user menu,
3. click on logout options

Screenshots (if applicable)

Screen.Recording.2026-01-23.145438.mp4

[linux-foundation-easycla]

The committers listed above are authorized under a signed CLA.

• ✅ login: alokdangre / name: Alok Dangre (277aef3, 4caf5c0, 524875d, a806ab8)

[k8s-ci-robot]

Welcome @alokdangre!

It looks like this is your first PR to kubernetes-sigs/headlamp 🎉. Please refer to our pull request process documentation to help your PR have a smooth ride to approval.

You will be prompted by a bot to use commands during the review process. Do not be afraid to follow the prompts! It is okay to experiment. Here is the bot commands documentation.

You can also check if kubernetes-sigs/headlamp has its own contribution guidelines.

You may want to refer to our testing guide if you run into trouble with your tests not passing.

If you are having difficulty getting your pull request seen, please follow the recommended escalation practices. Also, for tips and tricks in the contribution process you may want to read the Kubernetes contributor cheat sheet. We want to make sure your contribution gets all the attention it needs!

Thank you, and welcome to Kubernetes. 😃

[illume]

Thanks for this!

Can you please check the git commit guidelines in the development documentation and update your commit message? You can compare your message to other ones.

The frontend tests are failing in the GitHub check. Can you please try running the tests locally? Also, can you please add a storybook state for this?

[Copilot]

Pull request overview

Adds multi-cluster-aware user identity display and logout behavior in the TopBar, including a hook fix to keep multi-cluster selection derived from the URL in sync.

Changes:

• Updated TopBar to fetch/display per-cluster authenticated user info and provide per-cluster (and “logout all”) actions.
• Added SelfSubjectReview-based user info fetching (getClusterUserInfo) in the v1 cluster API layer.
• Fixed useSelectedClusters to react to pathname changes (not only cluster changes) for correct multi-cluster state updates.

Reviewed changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated 2 comments.

File	Description
frontend/src/lib/k8s/index.ts	Updates useSelectedClusters to recompute when location.pathname changes.
frontend/src/lib/k8s/api/v1/clusterApi.ts	Adds ClusterUserInfo + getClusterUserInfo() using the SelfSubjectReview API with fallback behavior.
frontend/src/components/App/TopBar.tsx	Implements multi-cluster user menu UX, per-cluster logout, and queries user info for selected clusters.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

Pull request overview

Copilot reviewed 7 out of 7 changed files in this pull request and generated 1 comment.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

Pull request overview

Copilot reviewed 7 out of 7 changed files in this pull request and generated 7 comments.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[alokdangre]

@illume sorry for that test error, i forgot to take snapshot, i have also added the requested changes

[alokdangre]

@illume ptal

[Copilot]

Pull request overview

Copilot reviewed 22 out of 22 changed files in this pull request and generated 1 comment.

Comments suppressed due to low confidence (2)

frontend/src/components/App/TopBar.stories.tsx:138

• The new SelfSubjectReview call in PureTopBar triggers a POST to /apis/authentication.k8s.io/v1/selfsubjectreviews whenever cluster is set. The TwoCluster story sets cluster: 'ak8s-desktop' but doesn’t register an MSW handler, which will be reported as an unhandled request by the Storybook test harness (see frontend/src/storybook.test.tsx unhandled request assertion). Add an MSW handler for this story (or define a default handler at the story/file level).

export const TwoCluster = PureTemplate.bind({});
TwoCluster.args = {
  appBarActions: [],
  logout: () => {},
  cluster: 'ak8s-desktop',
  clusters: { 'ak8s-desktop': '', 'ak8s-desktop2': '' },
};

frontend/src/setupTests.ts:71

• This file mocks window.localStorage when it’s missing/non-functional, but beforeEach calls localStorage.clear() (the global identifier). In environments where localStorage isn’t attached to the global scope (even if window.localStorage is defined), this will still throw. To make the setup robust, either set globalThis.localStorage = window.localStorage when mocking, or update the beforeEach to call window.localStorage.clear() (guarded by globalThis.window).

  if (!window.localStorage || typeof window.localStorage.getItem !== 'function') {
    Object.defineProperty(window, 'localStorage', {
      value: {
        getItem: vi.fn(() => null),
        setItem: vi.fn(),
        removeItem: vi.fn(),
        clear: vi.fn(),
        length: 0,
        key: vi.fn(),
      },
      writable: true,
    });
  }
}

beforeEach(() => {
  // Clears the database and adds some testing data.
  // Jest will wait for this promise to resolve before running tests.
  localStorage.clear();
});

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[illume]

🎉 thanks!

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: alokdangre, illume

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• OWNERS [illume]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[joaquimrocha]

I think this commit needs to be separated in several, even if within the same PR.
@illume was this what you had in mind in the issue that this PR relates too (it's not clear from the title and there's no body)?

I personally wonder why someone who want to log out from a single cluster that they are viewing as part of a group. I understand "Log out from all clusters" and I like that we have this option (we should have a confirmation by the user though), but not sure that having multiple "Log out from XYZ" is a good idea in terms of UX. What would be the use case?
I think a more expected approach is that users who want to log out from a certain cluster would use the context menu in the home table or click the cluster, then log out while viewing it.

[illume]

I think this commit needs to be separated in several, even if within the same PR.

@alokdangre yes, breaking this change up into small changes would make it easier to review/test and understand.

Are you able to break it up into separate commits?

Maybe using your list of changes as a rough guide? (or maybe you would have a better idea on how to break it up)

• Visual support for displaying authenticated users per cluster in TopBar.
• Implemented individual cluster logout functionality.
• Added SelfSubjectReview API support for fetching user info.
• Fixed multi-cluster selection state bug in useSelectedClusters hook.
• Improved logout UX to persist view on remaining clusters.

I personally wonder why someone who want to log out from a single cluster that they are viewing as part of a group. I understand "Log out from all clusters" and I like that we have this option (we should have a confirmation by the user though), but not sure that having multiple "Log out from XYZ" is a good idea in terms of UX. What would be the use case?
I think a more expected approach is that users who want to log out from a certain cluster would use the context menu in the home table or click the cluster, then log out while viewing it.

There is precedent for wanting to logout with only one account in a few apps when you can sign in multiple times. For example, inside MS products that allow multiple logins it's possible to select which login you want to sign-out with. I use this functionality personally in a few different websites.

But, maybe we need some more feedback on this part.

[ashu8912]

Hii @alokdangre the CI is failing

[alokdangre]

Hii @alokdangre the CI is failing

fixed , snapshot added

[alokdangre]

this fail is unusuall, becuase earlier the this tests where not failing but now it fails and locally all tests passes, im figuring it out

[joaquimrocha]

@illume ,

There is precedent for wanting to logout with only one account in a few apps when you can sign in multiple times. For example, inside MS products that allow multiple logins it's possible to select which login you want to sign-out with. I use this functionality personally in a few different websites.

Sure, but this I would say is the equivalent of logging out of a cluster from the home view, which is showing all clusters there.
In this PR we are saying that users group clusters together (which do not get saved anywhere, it's an intentional and temporary measure), and from this aggregated view they want to log out from a single cluster.

I would err on not providing this option and instead just the "Log out of these grouped clusters" if we need a log out from all while visualizing a group of clusters.