You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@joar Wonder if you have any insight here. There is a bug in the current code for me. If I kubectl edit a PersistentVolume, k8s-snapshots will not recognize that change. It will understand if I edit a PersistentVolumeClaim.
So I was looking into this, and I noticed that for both watch threads, it is actually quering the same resource, namely the last one that is starting watching (here, I turned it around, that is why it's watching the volumes, not the claims):
@joar Wonder if you have any insight here. There is a bug in the current code for me. If I
kubectl edit
a PersistentVolume, k8s-snapshots will not recognize that change. It will understand if I edit aPersistentVolumeClaim
.So I was looking into this, and I noticed that for both watch threads, it is actually quering the same resource, namely the last one that is starting watching (here, I turned it around, that is why it's watching the volumes, not the claims):
Correspondingly, if I log the actual events we receive, they are always
PersistentVolume
updates, even if it's a PersistentVolumeClaim watch thread:Now the thing that kind of blows my mind:
If I change
Kubernetes.watch
from:to
It works. EVERY TIME. Recording to proof it: http://recordit.co/HIBKNSNlXS
How can that be?
The text was updated successfully, but these errors were encountered: