Xun Jiang/Bruce Jiang
Xun Jiang/Bruce Jiang
Close for now. If any update, feel free to reopen
@matthiasritter Sorry for late response. Recently, Velero team is busy with v1.10 feature developing and v1.9.1 bug fixing. What is the version of Azure plugin you are using with Velero...
I thought this issue was caused by `azure.BearerAuthorizer#WithAuthorization: Failed to refresh the Token for request`. According to your recent uploaded log, looks like this issue happens intermittently after Azure plugin...
After taking another look, I found the HarshiCorp go-plugin version is already updated for this version of Azure plugin. Currently I couldn't find the reason why plugin process exited during...
Is the backup ended up with Failed status? Could you post the backup's Status section?
Need to also consider Item Action progress #5108 in RIA v2.
There is already an issue to address this #5146, and the fix was already cherry-picked into v1.9.1, but the thing looks a little surprising to me is ingress's API path:...
I will investigate more on this. Looks like this is related to the discoveryClient of client-go using by Velero to traverse all GVR from kube-apiserver.
@maartenjanvangool Checked discoveryClient implementation, it iterates through the kube-apiserver's "https:///apis/" to discover all available resources. I checked the resources on my developing GKE v1.22 cluster. ``` kubectl api-resources | grep...
I also didn't expected. Of course, the API deprecation and stopping serve are very clear in documents, but it's not easy for code logic to know how to do that....