frontend: pods: fix status icon stuck on warning after pod becomes ready

[nidhi-9900]

Summary

The pod status icon in the list view was getting stuck on warning even after the pod was Running and healthy. It only fixed itself after a page refresh. The issue was that getValue was only returning the reason string ("Running"), which stayed the same even when the Ready condition changed : so the table never re-rendered. Added the Ready condition status to the return value so it picks up the change.

Related Issue

Fixes #4905

Changes

• Updated getValue in the status column in frontend/src/components/pod/List.tsx to return both the reason and the Ready condition status
• Earlier it only returned the reason string which was "Running" in both warning and success states, so nothing triggered a re-render

Steps to Test

1. Start Headlamp locally
2. Go to Workloads → Pods
3. Run kubectl create deployment nginx-test --image=nginx
4. Watch the pod without refreshing the page
5. Icon should turn green when pod becomes ready

Notes for the Reviewer

• Only List.tsx is changed
• Snapshot files changed too but that's just MUI CSS class names, nothing to do with this fix

[linux-foundation-easycla]

The committers listed above are authorized under a signed CLA.

• ✅ login: nidhi-9900 / name: Nidhi Sharma (cf7aedf, fa2d5f6)

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: nidhi-9900
Once this PR has been reviewed and has the lgtm label, please assign illume for approval. For more information see the Code Review Process.

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

Details

Needs approval from an approver in each of these files:

• OWNERS

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

[k8s-ci-robot]

Welcome @nidhi-9900!

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. 😃

[sniok]

thanks for the PR, the code looks good but could you make sure not to include a merge commit