Robert Ruf

> It is not addressing a general IPAM approach for CAPV because that is under discussion in the CAPI community. Thanks for clearification. I can't wait to see the CAPI...

The default of having the k8s-ci-robot close issues after X days killed _many_ useful improvement suggestions it seems. I doubt this is helpful, you're losing alot of good user feedback....

/lifecycle frozen

/reopen

@MaxRink except you fixed the issue could you please `/reopen`? I'm not allowed to do so since I'm not the original author.

@neolit123 since @MaxRink isn't responding do you mind re-opening? I don't think this issue is solved yet.

I think I found the smoking gun why NTP is not applied. It seems like it's a issue with the pre-build Photon image: ```json root [ /var/lib/cloud/data ]# cat result.json...

```log systemctl status cloud-config.service ● cloud-config.service - Apply the settings specified in cloud-config Loaded: loaded (/lib/systemd/system/cloud-config.service; enabled; vendor preset: enabled) Drop-In: /etc/systemd/system/cloud-config.service.d └─boot-order.conf Active: failed (Result: exit-code) since Thu 2021-12-30...

We're currently using the latest pre-build [Photon 3 with Kubernetes 1.20.1](https://storage.googleapis.com/capv-images/release/v1.20.1/photon-3-kube-v1.20.1.ova). I'll check what cloud-init version it does use and let you know. P.S.: I also noticed this strange behaviour,...

As a workaround you can add `insecure-flag = true` to the `[Global]` section of the `csi-vsphere.conf` file of the `Secret:csi-vsphere-config` resource