Frontend: Pod: Added Deeplink compatibility for viewing logs

[mudit06mah]

Summary

This PR let's users to add ?view=logs to the URL to get logs for a pod.

Related Issue

Fixes #4348

Changes

Changed Details.tsx to check for query params, if found it activates log window.

Steps to Test

Through Deeplink:

• For any pod, go to: /c/{cluster}/pods/{namespace}/{pod-name}?view=logs, it opens up the logs for that particular pod.

From client Side:

• Open browser console for the pod Details page and write: window.history.pushState({}, '', window.location.pathname + '?view=logs');
• Then to dispatch that event to the router, add: window.dispatchEvent(new PopStateEvent('popstate'));

Screenshots (if applicable)

[mudit06mah]

This PR passes all tests and is ready to be merged.

[mudit06mah]

@sniok It appears I was unaware of i18n translation.

This PR should pass without any errors now :)

[Copilot]

Pull request overview

Adds support for deep-linking directly into a Pod’s logs view via ?view=logs, so opening a pod details URL with that query param automatically launches the logs activity.

Changes:

• Parse the view query parameter in PodDetails and auto-launch logs when view=logs.
• Refactor the “Show Logs” action handler to reuse a shared launchLogs helper.
• Normalize/move the Logs i18n glossary key placement across multiple locales.

Reviewed changes

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

Show a summary per file

File	Description
frontend/src/components/pod/Details.tsx	Adds view=logs query-param handling and refactors log-launching into a helper used by both the button and deep link.
frontend/src/i18n/locales/en/glossary.json	Moves/ensures the Logs key exists in the expected position.
frontend/src/i18n/locales/de/glossary.json	Moves the Logs key entry for consistency.
frontend/src/i18n/locales/es/glossary.json	Moves the Logs key entry for consistency.
frontend/src/i18n/locales/fr/glossary.json	Moves the Logs key entry for consistency.
frontend/src/i18n/locales/hi/glossary.json	Moves the Logs key entry for consistency.
frontend/src/i18n/locales/it/glossary.json	Moves the Logs key entry for consistency.
frontend/src/i18n/locales/ja/glossary.json	Moves the Logs key entry for consistency.
frontend/src/i18n/locales/ko/glossary.json	Moves the Logs key entry for consistency.
frontend/src/i18n/locales/pt/glossary.json	Moves the Logs key entry for consistency.
frontend/src/i18n/locales/ta/glossary.json	Moves the Logs key entry for consistency.
frontend/src/i18n/locales/zh/glossary.json	Moves the Logs key entry for consistency.
frontend/src/i18n/locales/zh-tw/glossary.json	Moves the Logs key entry for consistency.

---

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

[mudit06mah]

@illume I have made the changes suggested by copilot.

[Copilot]

Pull request overview

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

---

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

[illume]

Looking good. Thanks for those changes 🎉

Can you please answer the two questions I left? After you update the testing scenarios in the PR description I will manually test it.

[mudit06mah]

@illume @sniok I have made all the changes mentioned by copilot and maintainers and ran all tests as well. Can you please review this again?

[Copilot]

Pull request overview

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

---

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

[illume]

Thanks @ranjit-parva for the review/testing.

[mudit06mah]

@illume Made all changes suggested by copilot, Please review this again 👾

[illume]

🎉 thanks!

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: illume, mudit06mah, ranjit-parva

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