-
Notifications
You must be signed in to change notification settings - Fork 1
Tenant picker shown on cluster-scoped /admin pages #32
Copy link
Copy link
Open
Labels
area/consoleIssues or PRs related to apps/console — routes, detail pages, marketplace, command paletteIssues or PRs related to apps/console — routes, detail pages, marketplace, command palettearea/tenantsIssues or PRs related to tenant context, tenant-namespace scoping, multi-tenancyIssues or PRs related to tenant context, tenant-namespace scoping, multi-tenancykind/bugCategorizes issue or PR as related to a bugCategorizes issue or PR as related to a bugpriority/backlogGeneral backlog priority. Lower than priority/important-longtermGeneral backlog priority. Lower than priority/important-longterm
Description
Metadata
Metadata
Assignees
Labels
area/consoleIssues or PRs related to apps/console — routes, detail pages, marketplace, command paletteIssues or PRs related to apps/console — routes, detail pages, marketplace, command palettearea/tenantsIssues or PRs related to tenant context, tenant-namespace scoping, multi-tenancyIssues or PRs related to tenant context, tenant-namespace scoping, multi-tenancykind/bugCategorizes issue or PR as related to a bugCategorizes issue or PR as related to a bugpriority/backlogGeneral backlog priority. Lower than priority/important-longtermGeneral backlog priority. Lower than priority/important-longterm
Type
Fields
Give feedbackNo fields configured for issues without a type.
The subtitle tenant picker (
Breadcrumb, rendered unconditionally at apps/console/src/App.tsx:49) appears on every route, including the cluster-scoped/admin/*Capacity pages (Cluster, Nodes, Storage). Selecting a tenant there has no effect — those views are cluster-wide — so the control is misleading.Suggested fix: hide the picker when
pathname.startsWith("/admin")(or render it only for tenant-scoped areas). The per-resource drill-down's tenant scoping is data-side and independent of this picker, so hiding it does not affect those pages.