Unbound PVC still shown as "OK"

[davidmirror-ops]

What steps did you take and what happened:
[A clear and concise description of what the bug is, and what commands you ran.)

I deployed a workload in a local cluster and introduced an error: the PVC spec calls a Storage Class that doesn't exist. The workload is not working, the PVC is not bound but Octant shows it in a "OK" state which can be confusing for troubleshooting.

What did you expect to happen:
Octant should reflect the accurate status of a PVC
Anything else you would like to add:

Environment:

• Octant version (use octant version): 0.21.0
• Kubernetes version (use kubectl version): 1.21
• OS (macOS 10.15, Windows 10, Ubuntu 19.10 etc): macOS 11.3.1

[wwitzel3]

We may benefit from doing #381 first? If we had the list of storage classes, this would let us hint that it was non-existent.

[wwitzel3]

Extend the PVC printer to look at status and explicitly inform the user that their PVC is Unbound and potentially corelate that with recent events.

[wwitzel3]

3 areas for UI

• resource viewer
• summary
• list

who ever picks this up, please work with @mklanjsek to determine a good starting point for UI especially with resource viewer

[ftovaro]

To be honest this one looks really interesting, if is possible I'd like to take it and work it together with @mklanjsek if he's ok with it

[davidmirror-ops]

This is what i see from kubectl:

davidespejo@daespejo-a01 code % kubectl get pvc
NAME        STATUS    VOLUME   CAPACITY   ACCESS MODES STORAGECLASS       AGE
www-web-0   Pending                                      my-storage-class   16s

[wwitzel3]

@ftovaro Checking to make sure you have all the info you need to start on this issue?

[ftovaro]

@davidmirror-ops is it possible to share the config file of the pvc?

[davidmirror-ops]

sure @ftovaro

kind: PersistentVolumeClaim
apiVersion: v1
metadata:
 name: www-web-0
  
spec:
 storageClassName: "my-storage-class"
 accessModes:
  - ReadWriteOnce
 resources:
  requests:
   storage: 2Gi