Deepthi Sigireddi

This sounds great, and much safer than #7825. We'll still have put in BOLD ALL-CAPS that people are assuming the risk of inconsistent schema. @vitessio/query-serving what sort of spurious bug...

`vtgate_tablet_healthcheck_cache` was fixed in #10961. Totally unrelated, so we can merge this.

We are now at 1.22+, hence no longer relevant. Please re-open if you have problems with newer k8s versions.

@derekperkins what are your thoughts on this?

Upgrade/downgrade tests are failing. I'd assume they are unrelated. I believe the Query Serving one has been fixed on `main` so just needs a merge from main into the PR....

@dmuli welcome and thank you for the contribution. This project requires commits to be signed off. You can fix the commit in this PR by doing `git commit --amend --signoff`...

I missed this RFC when it first came up. Very interesting discussion. The one thing I will add is that for those running with vitess-operator, that would be a natural...

I think I understand why you can't use unspecified mode. You have the same table name in `legacy` and in `sites2023`. How did this come about? Usually, once tables have...

> Because dataAttributes is a reference table, copied to sites2023 Duh, of course. Will let Rohit keep looking into this :)

I like the proposal. We'll let @harshit-gangal and @systay chime in with any concerns and then we can make a decision on the path forward.