. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98 Comparisons to other storage options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98 names VitessAware big_tables NoOp bulk_insert_buffer_size NoOp debug NoOp default_storage_engine NoOp default_tmp_storage_engine NoOp innodb_strict_mode NoOp innodb_support_xa NoOp innodb_table_locks NoOp users via warning that settings are either ignored or modification was not allowed. E.g. default_storage_engine, debug, etc. Vitess Aware These are the system variables for which Vitess needs to change

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93 Comparisons to other storage options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93 names VitessAware big_tables NoOp bulk_insert_buffer_size NoOp debug NoOp default_storage_engine NoOp default_tmp_storage_engine NoOp innodb_strict_mode NoOp innodb_support_xa NoOp innodb_table_locks NoOp users via warning that settings are either ignored or modification was not allowed. E.g. default_storage_engine, debug, etc. Vitess Aware These are the system variables for which Vitess needs to change

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117 Comparisons to other storage options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118 names VitessAware big_tables NoOp bulk_insert_buffer_size NoOp debug NoOp default_storage_engine NoOp default_tmp_storage_engine NoOp innodb_strict_mode NoOp innodb_support_xa NoOp innodb_table_locks NoOp users via warning that settings are either ignored or modification was not allowed. E.g. default_storage_engine, debug, etc. Vitess Aware These are the system variables for which Vitess needs to change

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84 Comparisons to other storage options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84 enable_system_settings VitessAware big_tables NoOp bulk_insert_buffer_size NoOp debug NoOp default_storage_engine NoOp default_tmp_storage_engine NoOp innodb_strict_mode NoOp innodb_support_xa NoOp innodb_table_locks NoOp users via warning that settings are either ignored or modification was not allowed. E.g. default_storage_engine, debug, etc. Vitess Aware These are the system variables for which Vitess needs to change

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57 Comparisons to other storage options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57 names VitessAware big_tables NoOp bulk_insert_buffer_size NoOp debug NoOp default_storage_engine NoOp default_tmp_storage_engine NoOp innodb_strict_mode NoOp innodb_support_xa NoOp innodb_table_locks NoOp ensure it is in your PATH. For example, on Linux: curl -LO https://storage.googleapis.com/kubernetes -release/release/`curl -s https://storage.googleapis.com/kubernetes -release/release/stable.txt`/bin/linux/amd64/kubectl

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39 Comparisons to other storage options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39 ensure it is in your PATH. For example, on Linux: curl -LO https://storage.googleapis.com/kubernetes -release/release/`curl -s https://storage.googleapis.com/kubernetes -release/release/stable.txt`/bin/linux/amd64/kubectl access administrative web pages, start a proxy with: kubectl proxy --port=8001 Then use the following URLs: vtctld: http://localhost:8001/api/v1/namespaces/default/services/vtctld:web/proxy/app/ vtgate:

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45 Comparisons to other storage options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45 ensure it is in your PATH. For example, on Linux: curl -LO https://storage.googleapis.com/kubernetes -release/release/`curl -s https://storage.googleapis.com/kubernetes -release/release/stable.txt`/bin/linux/amd64/kubectl access administrative web pages, start a proxy with: kubectl proxy --port=8001 Then use the following URLs: vtctld: http://localhost:8001/api/v1/namespaces/default/services/vtctld:web/proxy/app/ vtgate:

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47 Comparisons to other storage options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47 Minikube. 2. Install kubectl and ensure it is in your PATH. For example on Linux: curl -LO https://storage.googleapis.com/kubernetes -release/release/v1.15.0/bin/linux/amd64/kubectl 24 3. Install Helm 2: /vitess/zone1 39 add zone1 CellInfo etcd start done... enter etcd2 env Starting vtctld... Access vtctld web UI at http://morgox1:15000 Send commands with: vtctlclient -server morgox1:15999 ... enter etcd2 env

users can. VTAdmin consists of two components: 1. A web interface - VTAdmin-web 2. A server - VTAdmin-api 5 Vitess Security Audit, 2023 The web interface connects to the server which in turn forwards VTAdmin-api level, not VTAdmin-web; VTAdmin-web is merely a client. In other words, authentication and authorization are not enforced when using the web UI - VTAdmin-web - but when the web UI communicates with the boundaries for VTAdmin. We first consider the trust boundaries of VTAdmin-web and then of VTAdmin-api. VTAdmin-web VTAdmin-web is meant to be deployed in a trusted environment, meaning that an attacker

+ Forks 8,000 + Stars 4 Key Adopters YouTube in 2010 2013 Storage Engine running as Stateless Application Stateless Storage 8 VITESS.IO 2015 9 VITESS.IO Oldest, since 2016 Kubernetes Workloads is that all MySQL at Slack is run behind Vitess. There’s no other bet we’re making in terms of storage in the foreseeable future.” Michael Demmer, Principal Engineer, Slack 17 VITESS.IO Architecture