-
-
Notifications
You must be signed in to change notification settings - Fork 35
Open
Description
Here is an example of the PV/PVC that does exists in kubernetes state, yet it's not used (nor exists in AWS volumes)
➜ k get pvc -n metrics
NAME STATUS VOLUME CAPACITY ACCESS MODES STORAGECLASS AGE
grafana-persistent-storage Bound pvc-1395291c-d89b-11e9-8a64-0a4976158cfe 1Gi RWO gp2 398d
➜ k describe pv pvc-1395291c-d89b-11e9-8a64-0a4976158cfe
Name: pvc-1395291c-d89b-11e9-8a64-0a4976158cfe
Labels: failure-domain.beta.kubernetes.io/region=eu-central-1
failure-domain.beta.kubernetes.io/zone=eu-central-1c
Annotations: kubernetes.io/createdby: aws-ebs-dynamic-provisioner
pv.kubernetes.io/bound-by-controller: yes
pv.kubernetes.io/provisioned-by: kubernetes.io/aws-ebs
Finalizers: [kubernetes.io/pv-protection]
StorageClass: gp2
Status: Bound
Claim: metrics/grafana-persistent-storage
Reclaim Policy: Delete
Access Modes: RWO
VolumeMode: Filesystem
Capacity: 1Gi
Node Affinity:
Required Terms:
Term 0: failure-domain.beta.kubernetes.io/zone in [eu-central-1c]
failure-domain.beta.kubernetes.io/region in [eu-central-1]
Message:
Source:
Type: AWSElasticBlockStore (a Persistent Disk resource in AWS)
VolumeID: aws://eu-central-1c/vol-0b92b7db07b87b3e8
FSType: ext4
Partition: 0
ReadOnly: false
Events: <none>
➜ aws ec2 describe-volumes --volume-ids vol-0b92b7db07b87b3e8
An error occurred (InvalidVolume.NotFound) when calling the DescribeVolumes operation: The volume 'vol-0b92b7db07b87b3e8' does not exist.
would be nice to see output for these PV, PVCs with POD column empty
rudolfbyker
Metadata
Metadata
Assignees
Labels
No labels