kingnarmer

I am getting same error deploying kafka cluster.

I upgraded to velero 1.13 and then started getting errors below. I tired first successful against empty S3 bucket then failed on second backup . I am running velero with...

I was able to get backup to run successfully by adding this section to chart input with velero running on read-only rootfs. ``` extraVolumes: - emptyDir: {} name: udmrepo -...

@blackpiglet I use kopia as uploader. I didn't make any change to whatever default user is used in container.

I am getting same error with 2.10.2.

@sba30 Yes , we use vsphere to build cluster VMs.

Thanks , what might have caused this behavior? I am tying to avoid this behavior on prod clusters if possible.

I tried setting `rfc2136-batch-change-size=1` without success. ``` time="2024-03-26T13:00:37Z" level=info msg="Instantiating new Kubernetes client" time="2024-03-26T13:00:37Z" level=info msg="Using inCluster-config based on serviceaccount-token" time="2024-03-26T13:00:37Z" level=info msg="Created Kubernetes client https://10.43.0.1:443" time="2024-03-26T13:00:37Z" level=info msg="Configured RFC2136...

Please keep it open .

I have replication working from 2.8.2 to 2.10.1, only issue is that deleted images not replicated.