Marvin Beckers

> While creating this ticket I'm not sure whether our Nutanix setup is even functional It's not because we haven't set up any cross-datacenter connectivity yet.

Closing because Nutanix doesnt have a special control plane component (no CCM) and (node) version upgrades were at least tested with KubeOne. No datacenter to test this on is available...

Pretty sure I found a bug, seems to be reproducible: 1. Create a dualstack Kubernetes 1.24 cluster on Azure with Ubuntu as OS and without public IPs (konnectivity is enabled;...

Apart from the already observed issue, I couldn't find a combination of CNI, CNI version, Konnectvity/OpenVPN and node OS that was causing any problems on Azure.

I heavily suspect the observed behaviour when it comes to the perceived race condition is "working as intended", because VolumeAttachment objects are likely created and watched by kube-controller-manager and then...

/remove-lifecycle stale

What's the purpose of this ticket, can we maybe add a description? I looked at the epic but I'm not quite sure what kind of automation is meant here.

You don't have to screenshot the error message, you can click it to copy it to your clipboard :-)

/retest

/hold For api migration.