Comment 3 for bug 2073529

>So it's working on microk8s and EKS but not AKS????? Weird.

Yes exactly.

> They'd need get/describe yaml of the affected pods, plus status format yaml of the juju model before and after the upgrade operation.

Error is reproducible, so it shouldn't be hard to get any information. That being said, I deployed once more and attaching below what was asked for.
* juju status before refresh: https://pastebin.canonical.com/p/5DSzfmwp88/
* juju status after refresh: https://pastebin.canonical.com/p/tG29Qfhb8k/
* envoy operator pod: https://pastebin.canonical.com/p/TkBYzx4ZJW/
* envoy operator describe: https://pastebin.canonical.com/p/rwjSDJWZDm/
* katib controller operator pod: https://pastebin.canonical.com/p/nrZJXcSt2n/
* katib controller operator describe: https://pastebin.canonical.com/p/VdNz2CmpY5/
* kubeflow volumes pod: https://pastebin.canonical.com/p/8WCWYwGJFt/
* kubeflow volumes describe: https://pastebin.canonical.com/p/WRQpx8YXNb/

(re status-before-refresh, I scaled the apps to 0 and back to 1 before refreshing, that's why they have `/1` as units)

> How feasible it is to redeploy rather than upgrade?

It is, as noted in our [alternative upgrade path](https://docs.google.com/document/d/1Wg32O5PF8RMy7ng7hY9gX37lHnwmszyBt4D2lI_MSjQ/edit#heading=h.k8y9mwjyl482), even if it's not an ideal UX.