If we deploy a workload cluster and a vRouter with the same convention exists previously (in a shutdown state) with the same name, e.g. vr-one-cp-0 (e.g. due to this issue), the CAPONE controller will fail with the following message:
2025-10-21T09:56:55Z INFO KubeAPIWarningLogger metadata.finalizers: "onecluster.infrastructure.cluster.x-k8s.io": prefer a domain-qualified finalizer name including a path (/) to avoid accidental conflicts with other finalizer writers
2025-10-21T09:56:55Z ERROR Reconciler error {"controller": "onecluster", "controllerGroup": "infrastructure.cluster.x-k8s.io", "controllerKind": "ONECluster", "ONECluster": {"name":"one","namespace":"default"}, "namespace": "default", "name": "one", "reconcileID": "45064d27-a05c-4c03-89bb-362288b38e10", "error": "Spec.ControlPlaneEndpoint.Host must not be empty"}
sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller[...]).reconcileHandler
/home/aleix/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.19.6/pkg/internal/controller/controller.go:316
sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller[...]).processNextWorkItem
/home/aleix/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.19.6/pkg/internal/controller/controller.go:263
sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller[...]).Start.func2.2
/home/aleix/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.19.6/pkg/internal/controller/controller.go:224
If we deploy a workload cluster and a vRouter with the same convention exists previously (in a shutdown state) with the same name, e.g.
vr-one-cp-0(e.g. due to this issue), the CAPONE controller will fail with the following message: