Nick Meyer
Nick Meyer
Seeing the same.
There is some disparity here with the documentation, the difference it appears being that the documentation focuses on those keywords that can't be used as identifiers (so the _strict_ keywords)....
I was finally able to capture the podspec from the backup mover pod: ``` apiVersion: v1 kind: Pod metadata: creationTimestamp: "2024-06-28T01:58:54Z" labels: velero.io/data-upload: one-backup-8cv5q velero.io/exposer-pod-group: snapshot-exposer name: one-backup-8cv5q namespace: velero...
```I created a debug pod with a mount for /var/lib/kubelet/pods matching node-agent pod spec and was able to interact with no issue, so I do not believe this is an...
I also tried setting the `node-agent` container `securityContext` to `privileged: true` with no improvement.
I tried rolling back to Velero 1.13 as well, no improvement.
Verifying the correct directory: ```bash ➜ ~ talosctl ls -d3 -n go -Hl /var/lib/kubelet NODE MODE UID GID SIZE(B) LASTMOD NAME go drwx------ 0 0 215 B 1 day ago...
Yes, `node-agent` is run as root.
OK, making _some_ headway here. I'm fairly sure this message originates from a file in the kubevirt PVC that I'm trying to back up which symlinks back to `/var/lib/kubelet`: ```...
https://github.com/kubevirt/kubevirt-velero-plugin/issues/257