lensapp/lens

Add persistent volume claimref name and claimref namespace into persistent volume view

Open

#6425 opened on Oct 19, 2022

View on GitHub
 (1 comment) (1 reaction) (0 assignees)TypeScript (22,003 stars) (1,433 forks)batch import
area/uienhancementgood first issue

Description

What would you like to be added:

Add persistent volume claim reference name and persistent volume claim reference namespace into persistent volume view.

Why is this needed:

Missing column (one or two) that would make it easier to find the referencing claim and/or referencing namespace.

Commands to find the corresponding values:

  • kubectl get persistentvolume -o=custom-columns=NAME:.metadata.name,PVC_NAMESPACE:.spec.claimRef.namespace
  • kubectl get persistentvolume -o=custom-columns=NAME:.metadata.name,PVC_NAME:.spec.claimRef.name

I would expect persistent volume view to be/have something like (one column case):

Persistent Volume Name Persistent Volume Claim Reference
persistent_volume_XXX persistent_volume_claim_AAA_namespace/persistent_volume_claim_AAA_name
persistent_volume_YYY persistent_volume_claim_BBB_namespace/persistent_volume_claim_BBB_name
persistent_volume_ZZZ persistent_volume_claim_CCC_namespace/persistent_volume_claim_CCC_name

Column sorting should be based on namespace name as well as claim name.

Environment:

  • Lens: 6.1.0
    • Electron: 19.0.17
    • Chrome: 102.0.5005.167
    • Node: 16.14.2
  • Windows 10 Pro

Contributor guide

Tech stack
typescriptnodejs
Domain
frontenddevops
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
Basic knowledge of KubernetesFamiliarity with Lens codebaseTypeScript and React
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70
Research direction
The implementation would involve adding two new columns to the PersistentVolume table component in the Lens frontend. Similar implementations exist for other resources like PersistentVolumeClaims. Look at the existing table configuration and column definitions in the relevant component files (e.g., src/renderer/components/+storage/persistent volumes). The kubectl commands provided in the issue can be used to extract the data from the Kubernetes API response.