Vitali Henrichs

Still relevant @yue9944882

@PengpengSun Thanks. When I set `wait-cloudinit-timeout=300` cloud-init is able to finish execution before the reboot and the workflow is not terminated prematurely by deployPkg. Still requires a custom image.

@PengpengSun I am running on VMware Cloud Director 10.4. According to https://github.com/vmware/cluster-api-provider-cloud-director/issues/506 and the linked Slack thread it is currently to possible to use native cloud-init customization.

@PengpengSun I would appreciate if you could share the progress on this issue.

After looking at your issue, it doesn't seem to be related. To verify you can try if it works with [Ubuntu 22.04 20230518](https://cloud-images.ubuntu.com/releases/jammy/release-20230518/ubuntu-22.04-server-cloudimg-amd64.ova) and no longer works with [Ubuntu 22.04...

@PengpengSun Any news on the change you were working on?

I am also interested in this feature.

I have the same issue. As a workaround I extended the ClusterRoleBinding `csi-resizer-binding` in the `csi-controller.yaml` manifest by the `csi-vcd-node-sa` ServiceAccount: ``` kind: ClusterRoleBinding apiVersion: rbac.authorization.k8s.io/v1 metadata: name: csi-resizer-binding subjects:...

@arunmk does not work for me: ``` csi-vcd-nodeplugin-7s4tr csi-resizer I0503 05:28:11.488060 1 reflector.go:255] Listing and watching *v1.PersistentVolumeClaim from k8s.io/client-go/informers/factory.go:134 csi-vcd-nodeplugin-7s4tr csi-resizer W0503 05:28:11.490523 1 reflector.go:324] k8s.io/client-go/informers/factory.go:134: failed to list *v1.PersistentVolumeClaim:...

@arunmk Yes, same issue: ``` csi-vcd-nodeplugin-24z9g csi-resizer I0506 05:14:33.490748 1 reflector.go:255] Listing and watching *v1.Pod from k8s.io/client-go/informers/factory.go:134 csi-vcd-nodeplugin-24z9g csi-resizer W0506 05:14:33.491907 1 reflector.go:324] k8s.io/client-go/informers/factory.go:134: failed to list *v1.Pod: pods is...