JenTing

Yes, but the problem is the kubectl container image. You could refer to issue #339 for reference.

Leaving a note here, the bitnami/kubectl supports linux/arm64 from 1.25+ version.

We deprecated the `configuration.provider` but configured the provider in each backup storage location as well as in each volume snapshot location. Here is the [PR](https://github.com/vmware-tanzu/helm-charts/pull/413). Closing it.

We have decreased the crds/restores.yaml size in v1.10 version, closing this issue.

We deprecated the `configuration.provider` but configured the provider in each backup storage location as well as in each volume snapshot location. Here is the [PR](https://github.com/vmware-tanzu/helm-charts/pull/413). Closing it.

@flostru The helm chart can't guarantee the ordering, and the velero-plugin-for-vsphere requires the BSL is available. So, I think it's the velero-plugin-for-vsphere design. Is there any way the velero-plugin-for-vsphere could...

@phanikumar1210 Is the problem still occurring in your environment?

It needs the restic supports s309x platform, ref to https://github.com/restic/restic/issues/2780.

> Does this project help doing CA certificate rotation? > > > > https://kubernetes.io/docs/tasks/tls/manual-rotation-of-ca-certificates/ @alwaysastudent no, because kubeadm bootstrapped cluster CA certificate by default is 10 years, so we didn't...

Similar to the [issue](https://github.com/argoproj/argo-cd/issues/11458) which is address in the later version.