. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62 VTTablet YAML configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TabletServer specific configs can inherit and override the original ones. The input file format could be yaml. Also, this is a good opportunity for us to come up with better names. Since the config option is -tablet_config=filename.yaml, then we can branch off into code that reads the yaml file and initializes the configs from there. The code will load the global part of the yaml into a “global” Config. For

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70 VTTablet YAML configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TabletServer specific configs can inherit and override the original ones. The input file format could be yaml. Also, this is a good opportunity for us to come up with better names. Since the config option is ‘-tablet_config=’filename.yaml”, then we can branch off into code that reads the yaml file and initializes the configs from there. The code will load the global part of the yaml into a “global” Config.

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68 VTTablet YAML configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TabletServer specific configs can inherit and override the original ones. The input file format could be yaml. Also, this is a good opportunity for us to come up with better names. Since the config option is -tablet_config=filename.yaml, then we can branch off into code that reads the yaml file and initializes the configs from there. The code will load the global part of the yaml into a “global” Config. For

com:coreos/etcd-operator.git cd etcd-operator example/rbac/create_role.sh kubectl create -f example/deployment.yaml 4. Install the MySQL client locally. For example, on Ubuntu: apt-get install mysql-client 5. Install a group of yaml files. The first digit of each file name indicates the phase of example. The next two digits indicate the order in which to execute them. For example, 101_initial_cluster.yaml is the first the first phase. We shall execute that now: helm install ../../helm/vitess -f 101_initial_cluster.yaml This will bring up the initial Vitess cluster with a single keyspace. Verify cluster Once successful

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93 VTTablet YAML configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TabletServer specific configs can inherit and override the original ones. The input file format could be yaml. Also, this is a good opportunity for us to come up with better names. Since the config option is -tablet_config='filename.yaml', then we can branch off into code that reads the yaml file and initializes the configs from there. The code will load the global part of the yaml into a “global” Config.

a group of yaml files. The first digit of each file name indicates the phase of example. The next two digits indicate the order in which to execute them. For example, 101_initial_cluster.yaml is the first /../helm/vitess -f 101_initial_cluster.yaml You should see output similar to the following: $ helm install vitess ../../helm/vitess -f 101_initial_cluster.yaml NAME: vitess LAST DEPLOYED: Tue Apr 14 vitess/examples/operator Install the operator: kubectl apply -f operator.yaml Bring up an initial cluster In this directory, you will see a group of yaml files. The first digit of each file name indicates the phase

a group of yaml files. The first digit of each file name indicates the phase of example. The next two digits indicate the order in which to execute them. For example, 101_initial_cluster.yaml is the first /../helm/vitess -f 101_initial_cluster.yaml You should see output similar to the following: $ helm install vitess ../../helm/vitess -f 101_initial_cluster.yaml NAME: vitess LAST DEPLOYED: Tue Apr 14 vitess/examples/operator Install the operator: kubectl apply -f operator.yaml Bring up an initial cluster In this directory, you will see a group of yaml files. The first digit of each file name indicates the phase

a group of yaml files. The first digit of each file name indicates the phase of example. The next two digits indicate the order in which to execute them. For example, 101_initial_cluster.yaml is the first ./helm/vitess -f 101_initial_cluster.yaml You should see output similar to the following: 28 $ helm install vitess ../../helm/vitess -f 101_initial_cluster.yaml NAME: vitess LAST DEPLOYED: Tue Apr the master using the -force flag: helm upgrade vitess ../../helm/vitess/ -f 201_customer_tablets.yaml After a few minutes the pods should appear running: $ kubectl get pods,jobs NAME READY STATUS RESTARTS

attackerʼs options are therefore limited, however, an impactful vector could be controlling the rbac.yaml which could allow an attacker to assign permission to themselves, thus controlling the authentication