feat: add a button to clear logs in the pod logs viewer

[gcadoret]

Description

This PR introduces a small UX improvement to the pod logs viewer by adding a "Clear logs" button.

Currently, users need to refresh or navigate away to reset the displayed logs. This change provides a quick and intuitive way to clear the log output directly from the UI, which improves usability when working with noisy or continuously updating logs.

Scope

• UI-only change (no backend or API impact)
• Does not modify existing log fetching or filtering logic
• Adds unit test coverage for the new behavior

Motivation

When debugging applications, logs can quickly become cluttered. Providing a clear action helps users focus on new incoming logs without extra navigation steps.

---

Checklist

• This does not need to be in the release notes (small UX improvement)
• The title of the PR is clear and follows the guidelines
• Closes [ISSUE #] (not applicable)
• UI updated (CLI not impacted)
• Documentation update required? (not required)
• Documentation updated (not required)
• DCO sign-off added to commits
• Unit and/or e2e tests added
• Build is green
• This PR includes a clear explanation of the change

[bunnyshell]

❌ Preview Environment undeployed from Bunnyshell

Available commands (reply to this comment):

• 🚀 /bns:deploy to deploy the environment

[gcadoret]

Friendly ping: this PR is ready for review. All checks are passing, and I’d appreciate feedback from a code owner when you have a moment. Thanks!

[Qodo-Free-For-OSS]

Hi, The unit test mocks the shared Button as a native <button disabled>, so it will pass even if the real Button ignores disabled, hiding the production bug.

Severity: action required | Category: reliability

How to fix: Align mock with real Button

Agent prompt to fix - you can give this to your LLM of choice:

Issue description

The test double for Button behaves differently from the real component, so it can’t catch bugs related to disabled semantics.

Issue Context

The mock currently forwards disabled to a native <button>, while the real Button doesn’t.

Fix Focus Areas

• ui/src/app/applications/components/pod-logs-viewer/pod-logs-viewer.test.tsx[41-46]
• ui/src/app/shared/components/button.tsx[6-36]

What to change

• Prefer fixing Button to correctly forward disabled (see other finding).
• Then update the test mock to match the real Button behavior (or, better, don’t mock Button at all if feasible).
• Add an assertion that clicking the clear button when disabled does not invoke onClear (i.e., simulate click and ensure logs remain unchanged).

---

Qodo code review - free for open-source.

[gcadoret]

/review

[gvago]

Hey @gcadoret,

Qodo FOSS is not yet installed in argo.
One of the mainteners needs to add it.
But FYI, once installed, qodo is automatically triggered and the correct manual trigger (if needed) is "/agentic_review"

Cheers
Vago

[gcadoret]

@gvago

ok thanks you !

Cheers
Guillaume

[gcadoret]

Hello @gvago
Are you a code reviewer ? Could you please take a look on it ?
Thanks in advance !
Cheers,