Traefik Mesh control plane and Traefik Proxy data plane interoperability when rolling back after a CRD schema change

The goal is to determine whether Traefik Mesh can safely roll back its control plane to an earlier version after a CRD schema bump without requiring administrators to manually convert existing MeshService, TrafficSplit, or MeshPolicy objects.

Currently the controller lacks a built‑in conversion webhook, so upgrading the controller forces a manual migration step; rolling back before that step can cause the API server to reject the old CRD version, leading to reconciliation loops or stale sidecar configurations.

Should Traefik Mesh add a version‑aware conversion webhook for its CRDs? What operational trade‑offs would such a webhook introduce compared with the existing documentation‑driven migration process? How would the presence of a conversion webhook affect the rollback procedure and guarantee compatibility between control‑plane and data‑plane versions?