Feat/infra monitoring k8s volume

[amlannandy]

Summary

Related Issues / PR's

Screenshots

NA

Affected Areas and Manually Tested Areas

---

Important

Add Kubernetes volumes monitoring feature with new API calls, UI components, styles, and utilities.

• API Changes:
  • Add getK8sVolumesList function in getK8sVolumesList.ts to fetch Kubernetes volumes data.
  • Update API calls in getK8sDaemonSetsList.ts, getK8sJobsList.ts, and getsK8sStatefulSetsList.ts to use axios.
• UI Components:
  • Add K8sVolumesList component in K8sVolumesList.tsx for displaying volumes.
  • Add VolumeDetails component in VolumeDetails.tsx for detailed view of a volume.
  • Update InfraMonitoringK8s.tsx to include volumes in the monitoring categories.
• Styles:
  • Add styles for volumes in K8sVolumesList.styles.scss and entityDetails.styles.scss.
• Utilities and Constants:
  • Add utility functions in utils.tsx for handling volume data.
  • Update constants.ts to include volume-related configurations and mappings.
• Hooks:
  • Add useGetK8sVolumesList hook in useGetK8sVolumesList.ts for fetching volume data using React Query.

^{This description was created by for 6fa7e39. It will automatically update as commits are pushed.}

[ellipsis-dev]

👍 Looks good to me! Reviewed everything up to 6fa7e39 in 2 minutes and 18 seconds

More details

• Looked at 5600 lines of code in 41 files
• Skipped 0 files when reviewing.
• Skipped posting 9 drafted comments based on config settings.

1. frontend/src/container/InfraMonitoringK8s/Volumes/VolumeDetails/VolumeDetails.tsx:34

• Draft comment:
  The conversion factor for nanoseconds to milliseconds should be 1000000, not 1000000000. Please update the conversion logic accordingly.
• Reason this comment was not posted:
  Decided after close inspection that this draft comment was likely wrong and/or not actionable:

1. To convert from nanoseconds to milliseconds, we need to divide by 1,000,000 (1e6) since 1ms = 1,000,000ns. 2. However, looking at the variable names (startMs, endMs), these might actually be meant to be in seconds, not milliseconds. 3. To convert from nanoseconds to seconds, we divide by 1,000,000,000 (1e9). 4. The current code uses 1e9 consistently, suggesting it's intentionally converting to seconds.
   I could be wrong about the intended unit - maybe these times really should be in milliseconds. Without seeing how these values are used by other components, I can't be 100% certain.
   The consistent use of 1e9 throughout the file and the fact that Unix timestamps are typically in seconds strongly suggests these are meant to be second-based timestamps, not milliseconds.
   The comment appears to be incorrect. The code is likely intentionally converting to seconds, not milliseconds, so the 1000000000 divisor is correct.

2. frontend/src/container/InfraMonitoringK8s/Volumes/VolumeDetails/VolumeDetails.tsx:37

• Draft comment:
  The conversion factor for nanoseconds to milliseconds should be 1000000, not 1000000000. Please update the conversion logic accordingly.
• Reason this comment was not posted:
  Marked as duplicate.

3. frontend/src/container/InfraMonitoringK8s/Volumes/VolumeDetails/VolumeDetails.tsx:66

• Draft comment:
  The conversion factor for nanoseconds to milliseconds should be 1000000, not 1000000000. Please update the conversion logic accordingly.
• Reason this comment was not posted:
  Marked as duplicate.

4. frontend/src/container/InfraMonitoringK8s/Volumes/VolumeDetails/VolumeDetails.tsx:67

• Draft comment:
  The conversion factor for nanoseconds to milliseconds should be 1000000, not 1000000000. Please update the conversion logic accordingly.
• Reason this comment was not posted:
  Marked as duplicate.

5. frontend/src/container/InfraMonitoringK8s/Volumes/VolumeDetails/VolumeDetails.tsx:85

• Draft comment:
  The conversion factor for nanoseconds to milliseconds should be 1000000, not 1000000000. Please update the conversion logic accordingly.
• Reason this comment was not posted:
  Marked as duplicate.

6. frontend/src/container/InfraMonitoringK8s/Volumes/VolumeDetails/VolumeDetails.tsx:86

• Draft comment:
  The conversion factor for nanoseconds to milliseconds should be 1000000, not 1000000000. Please update the conversion logic accordingly.
• Reason this comment was not posted:
  Marked as duplicate.

7. frontend/src/container/InfraMonitoringK8s/Volumes/VolumeDetails/VolumeDetails.tsx:106

• Draft comment:
  The conversion factor for nanoseconds to milliseconds should be 1000000, not 1000000000. Please update the conversion logic accordingly.
• Reason this comment was not posted:
  Marked as duplicate.

8. frontend/src/container/InfraMonitoringK8s/Volumes/VolumeDetails/VolumeDetails.tsx:107

• Draft comment:
  The conversion factor for nanoseconds to milliseconds should be 1000000, not 1000000000. Please update the conversion logic accordingly.
• Reason this comment was not posted:
  Marked as duplicate.

9. frontend/src/container/InfraMonitoringK8s/Volumes/utils.tsx:137

• Draft comment:
  Use design tokens or predefined color constants instead of hardcoding color values for consistency.
• Reason this comment was not posted:
  Comment looked like it was already resolved.

Workflow ID: wflow_B3GVR8qJm1sc3yPz

---

You can customize Ellipsis with 👍 / 👎 feedback, review rules, user-specific overrides, quiet mode, and more.