the `registry-location` field was missing in the `kube-control` relation from the 1.24/stable kubernetes-control-plane charm. Looking over that charm (as well as 1.25 and 1.26 releases) it may be possible to get this bug to occur again by deploying charmed kubernetes until it's completely active/idle.
Next, one would then deploy and relate the kubevirt charm with all its necessary relations. This may create the kube-control relation in such a way that the registry-location isn't provided.
the `registry-location` field was missing in the `kube-control` relation from the 1.24/stable kubernetes- control- plane charm. Looking over that charm (as well as 1.25 and 1.26 releases) it may be possible to get this bug to occur again by deploying charmed kubernetes until it's completely active/idle.
Next, one would then deploy and relate the kubevirt charm with all its necessary relations. This may create the kube-control relation in such a way that the registry-location isn't provided.