miscellaneous findings. In terms of resources, the test was completed by six members of the Cure53 team who worked within a time budget of eighteen days. The testers are considered very experienced assessment, a CNCF-typical setup was requested by the testers and provided by the development team. Besides furnishing Cure53 with a Kubernetes-based cluster, locally installed systems were also used interfaces and the system architecture, supported also by additional exchange with the development team, revealed a rather limited attack surface. This observation was later confirmed as the subsequent

modelling should be seen as an ongoing effort. Future security disclosures to the Vitess security team are opportunities to evaluate the threat model of the affected components. Most compromises of VTAdmin templates were only user-controlled in one of the cases. This case was triaged heavily and the Vitess team found that an attack vector was not possible. To guard against future issues with templating, Vitess well as for the Vitess team when triaging bug reports. The auditing team found two vulnerabilities during the audit, and the Vitess team were fast to respond to these. The Vitess team also extensively triaged

owners to auto-assign reviewers to a particular PR. If you have been granted membership to the Vitess team, you can add additional reviewers using the right-hand side pull request menu. During discussions system • Reply with a comment that contains LGTM (Looks Good To Me) Merging a Pull Request The Vitess team will merge your pull request after the PR has been approved and CI tests have passed. GitHub Workflow released as Open Source Vitess was created in 2010 to solve the MySQL scalability challenges that the team at YouTube faced. This section briefly summarizes the sequence of events that led to Vitess’ creation:

owners to auto-assign reviewers to a particular PR. If you have been granted membership to the Vitess team, you can add additional reviewers using the right-hand side pull request menu. During discussions system • Reply with a comment that contains LGTM (Looks Good To Me) Merging a Pull Request The Vitess team will merge your pull request after the PR has been approved and CI tests have passed. GitHub Workflow released as Open Source Vitess was created in 2010 to solve the MySQL scalability challenges that the team at YouTube faced. This section briefly summarizes the sequence of events that led to Vitess’ creation:

owners to auto-assign reviewers to a particular PR. If you have been granted membership to the Vitess team, you can add additional reviewers using the right-hand side pull request menu. During discussions system • Reply with a comment that contains LGTM (Looks Good To Me) Merging a Pull Request The Vitess team will merge your pull request after the PR has been approved and CI tests have passed. 24 GitHub released as Open Source Vitess was created in 2010 to solve the MySQL scalability challenges that the team at YouTube faced. This section briefly summarizes the sequence of events that led to Vitess’ creation:

owners to auto-assign reviewers to a particular PR. If you have been granted membership to the Vitess team, you can add additional reviewers using the right-hand side pull request menu. During discussions system • Reply with a comment that contains LGTM (Looks Good To Me) Merging a Pull Request The Vitess team will merge your pull request after the PR has been approved and CI tests have passed. GitHub Workflow released as Open Source Vitess was created in 2010 to solve the MySQL scalability challenges that the team at YouTube faced. This section briefly summarizes the sequence of events that led to Vitess’ creation:

owners to auto-assign reviewers to a particular PR. If you have been granted membership to the Vitess team, you can add additional reviewers using the right-hand side pull request menu. During discussions system • Reply with a comment that contains LGTM (Looks Good To Me) Merging a Pull Request The Vitess team will merge your pull request after the PR has been approved and CI tests have passed. 36 GitHub released as Open Source Vitess was created in 2010 to solve the MySQL scalability challenges that the team at YouTube faced. This section briefly summarizes the sequence of events that led to Vitess’ creation:

owners to auto-assign reviewers to a particular PR. If you have been granted membership to the Vitess team, you can add additional reviewers using the right-hand side pull request menu. During discussions system • Reply with a comment that contains LGTM (Looks Good To Me) Merging a Pull Request The Vitess team will merge your pull request after the PR has been approved and CI tests have passed. 38 GitHub released as Open Source Vitess was created in 2010 to solve the MySQL scalability challenges that the team at YouTube faced. This section briefly summarizes the sequence of events that led to Vitess’ creation:

owners to auto-assign reviewers to a particular PR. If you have been granted membership to the Vitess team, you can add additional reviewers using the right-hand side pull request menu. During discussions system • Reply with a comment that contains LGTM (Looks Good To Me) Merging a Pull Request The Vitess team will merge your pull request after the PR has been approved and CI tests have passed. 37 GitHub released as Open Source Vitess was created in 2010 to solve the MySQL scalability challenges that the team at YouTube faced. This section briefly summarizes the sequence of events that led to Vitess’ creation:

owners to auto-assign reviewers to a particular PR. If you have been granted membership to the Vitess team, you can add additional reviewers using the right-hand side pull request menu. During discussions system • Reply with a comment that contains LGTM (Looks Good To Me) Merging a Pull Request The Vitess team will merge your pull request after the PR has been approved and CI tests have passed. GitHub Workflow released as Open Source Vitess was created in 2010 to solve the MySQL scalability challenges that the team at YouTube faced. This section briefly summarizes the sequence of events that led to Vitess’ creation: