After further digging it was discovered that adding the k8s-cloud to the existing VM controller resolved the situation. Updating the workaround.
After further digging it was discovered that adding the k8s-cloud to the existing VM controller resolved the situation. Updating the workaround.