[Feature] Istio Add-on upgrade be integrated as part of the AKS Kubernetes version upgrade or a hook on Fleet Manager

We were planning an AKS version upgrade, and one of the required pre-checks is upgrading Istio addon. So, we are evaluating the upgrade path for AKS Istio Add-on revisions from asm-1-28 to asm-1-30.

1. Is there a possibility to leverage Fleet Manager or Fleet Hub to simplify and orchestrate Istio Add-on upgrades, similar to a minor version upgrade workflow? or plan to run hooks before AKS upgrades?
2. Can the Istio Add-on upgrade be integrated as part of the AKS Kubernetes version upgrade process?

Based on the documentation, the AKS Istio Add-on follows a revision-based canary upgrade model where a new control plane revision is installed alongside the existing revision, and workload namespaces must subsequently be migrated to the new revision. The migration involves relabeling namespaces and restarting workloads to pick up the new sidecar version

At larger scale, the operational burden becomes significant.