You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
After adding a repository the cluster is undefined #616
After adding a new repository, one will be redirected to a path like /#/repository/netbox.
If then going back to "installed" tab, the path will be something like /#/undefined/installed/ and it errors, as "undefined" is obviously not an existing cluster in our environment:
After clicking the banner away and selecting the current cluster everything is again working fine, but especially after an initial installation of helm-dashboard when I need to import quite many repositories, this is quite annoying.
I'd like to work on this issue! I've been investigating the routing locally and identified the root cause of the /undefined/installed/ redirection.
Findings:
The issue is caused by inconsistent path handling in the Header and RepositoryPage.
Switching from relative paths to root-relative paths in the navigation links, and standardizing how the context (cluster) parameter is handled, prevents losing the cluster name.
This also fixes URL segment doubling when adding new repositories.
I have a fix ready that ensures the cluster context is preserved across tab switches and after adding a new repository. Could you please assign this issue to me so I can submit a PR?
There is no formal assignment process, just bring the PR
Beware though that relative navigation is important for the cases where ingress exposes the application from unpredictable root.
Activity
undera commentedon Nov 5, 2025
Thanks for reporting. We would need somebody with ReactJS frontend skills to help on this.
Vedant5125 commentedon Jan 8, 2026
Hi @undera,
I'd like to work on this issue! I've been investigating the routing locally and identified the root cause of the
/undefined/installed/redirection.Findings:
HeaderandRepositoryPage.I have a fix ready that ensures the cluster context is preserved across tab switches and after adding a new repository. Could you please assign this issue to me so I can submit a PR?
Thanks!
undera commentedon Jan 8, 2026
There is no formal assignment process, just bring the PR
Beware though that relative navigation is important for the cases where ingress exposes the application from unpredictable root.
fix: maintain cluster context after adding repo (komodorio#616)
fix: maintain cluster context after adding repo (#616) (#641)