the requests to the Vitess internals: From https://vitess.io/docs/17.0/reference/vtadmin/architecture/ Authentication and authorization VTAdmin does two things when receiving incoming requests: 1) It validates the actor against the RBAC. As such, the flow of handling the permissions of incoming requests looks as such: Authentication Authentication in VTAdmin has the purpose of answering the question request has been authenticated and authorized, it will not cross any further trust boundaries. The requests made by VTAdmin-Web are unauthenticated and unauthorized until VTAdmin-api authenticates and authorizes

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40 Sending Pull Requests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . eligible to be promoted to master. Conventionally, these are reserved for serving live, user-facing requests (like from the website’s frontend). • rdonly - A MySQL replica that cannot be promoted to master add a Signed-off-by line. This is needed for the Developer Certificate of Origin. Sending Pull Requests Push your branch to the repository (and set it to track with -u): (new-feature) $ git push -u

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39 Sending Pull Requests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . eligible to be promoted to master. Conventionally, these are reserved for serving live, user-facing requests (like from the website’s frontend). • rdonly - A MySQL replica that cannot be promoted to master add a Signed-off-by line. This is needed for the Developer Certificate of Origin. Sending Pull Requests Push your branch to the repository (and set it to track with -u): (new-feature) $ git push -u

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38 Sending Pull Requests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . eligible to be promoted to master. Conventionally, these are reserved for serving live, user-facing requests (like from the website’s frontend). • rdonly - A MySQL replica that cannot be promoted to master add a Signed-off-by line. This is needed for the Developer Certificate of Origin. Sending Pull Requests Push your branch to the repository (and set it to track with -u): (new-feature) $ git push -u

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43 Sending Pull Requests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . eligible to be promoted to primary. Conventionally, these are reserved for serving live, user-facing requests (like from the website’s frontend). • rdonly - A MySQL replica that cannot be promoted to primary add a Signed-off-by line. This is needed for the Developer Certificate of Origin. Sending Pull Requests Push your branch to the repository (and set it to track with -u): (new-feature) $ git push -u

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26 Sending Pull Requests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . allows migrations to proceed in phases: first migrate rdonly and replica requests, one cell at a time, and finally migrate master requests. Served From During vertical resharding (moving tables out from one app to look for the tables to be moved in new_keyspace. Vitess will automatically redirect these requests to old_keyspace. 3. Perform a vertical split clone to copy data to the new keyspace and start filtered

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38 Sending Pull Requests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . eligible to be promoted to master. Conventionally, these are reserved for serving live, user-facing requests (like from the website’s frontend). • rdonly - A MySQL replica that cannot be promoted to master add a Signed-off-by line. This is needed for the Developer Certificate of Origin. Sending Pull Requests Push your branch to the repository (and set it to track with -u): (new-feature) $ git push -u

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21 Sending Pull Requests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . allows migrations to proceed in phases: first migrate rdonly and replica requests, one cell at a time, and finally migrate master requests. Served From During vertical resharding (moving tables out from one app to look for the tables to be moved in new_keyspace. Vitess will automatically redirect these requests to old_keyspace. 3. Perform a vertical split clone to copy data to the new keyspace and start filtered

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25 Sending Pull Requests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . allows migrations to proceed in phases: first migrate rdonly and replica requests, one cell at a time, and finally migrate master requests. Served From During vertical resharding (moving tables out from one app to look for the tables to be moved in new_keyspace. Vitess will automatically redirect these requests to old_keyspace. 3. Perform a vertical split clone to copy data to the new keyspace and start filtered