[BUG] Managed Clusters not displaying when itsData is null

[krishkumar84]

Description

The Managed Clusters page (/its) was not displaying any clusters even when valid Kubernetes contexts were present in the system. This occurred because the component wasn't properly handling the case where itsData is null in the API response.

Steps to Reproduce

1. Go to '/its' (Managed Clusters page)
2. Have a local Kubernetes cluster set up with name ending in "-kubeflex"
3. Observe that the clusters table is empty
4. Check the API response in browser console showing:
   {
   "clusters": ["kind-kubeflex"],
   "contexts": [{
   "name": "kind-kubeflex",
   "cluster": "kind-kubeflex"
   }],
   "currentContext": "kind-kubeflex",
   "itsData": null
   }

Expected Behavior

1. The Managed Clusters page should display local clusters when itsData is null
2. Clusters with names ending in "-kubeflex" should be visible in the table
3. Each cluster should show its name, labels, creation time, context, and status

Actual Behavior

1. The Managed Clusters page shows "Managed Clusters (0)"
2. The table is empty despite having valid clusters in the system
3. No error messages are displayed to the user

Screenshots or Logs

[Screenshot 1: Empty Managed Clusters table]

[Screenshot 2: API Response in Console]

Additional Context

The issue was caused by the component not having a fallback mechanism to handle local clusters when the itsData field is null. This particularly affects development environments where local Kubernetes clusters are being used.

[github-actions]

👋 Hello! @krishkumar84 Welcome to the Kubestellar.

We're excited to have you here! Please make sure to check out our contribution guide and feel free to join our Slack channel for any questions.