traefikmesh-controller: error reconciling MeshService: failed to get Service: services \"example-svc\" not found

Determine whether TraefikMesh should automatically create a default MeshService CRD for every Kubernetes Service that does not have an explicit MeshService definition, thereby preventing the reconciliation error \"failed to get Service\" when the controller watches for referenced Services.

This decision must balance operational simplicity against potential side‑effects such as unwanted resource creation, version‑specific behavior, and the need to preserve existing workflows where users rely on manual MeshService objects for fine‑grained control.

• Should the controller generate a MeshService CRD automatically when a Service is created and no matching MeshService exists?
• What criteria (e.g., namespace, labels, annotation) should decide which Services receive an auto‑generated MeshService?
• How would automatic MeshService creation impact existing deployments that already define MeshService objects manually?