Rimantas (Rimas) Mocevicius

master and agents `.tf` files need to use `element` in `subnet_id` as per `subnet_id = "${element(aws_subnet.public.*.id,count.index)}"` and those two merge conflicts resolved then PR is good to be merged

also can you make it optional please, thanks and master are not recommend to be spread around multi-az, they need to stay in one AZ

it is not really recommended to spread masters across multi-az (is more harm than good). bootstrap and master can stay in one zone by default e.g. `${aws_subnet.public.0.id}"` and the agents...

please remove `count = "${var.num_of_masters}"` from the `private-/public-agent.tf` files, so agent can be spread on all available zones in the region

LGTM cc @bernadinm I have tested such setup, not sure why CI fails there

@bernadinm can we merge this one? I been using this solution without isues

you cain check the VMs spec here https://github.com/mesosphere/dcos-kubernetes-quickstart/blob/master/resources/desired_cluster_profile.gcp That project is based on this one to make an easy way to try kubernetes on dc/os

I think it makes sense to rename it to `istio-base` as usually all of us have many helm repos for our use, so the helm chart should be named properly...

@lfittl I'm just looking an easy way to bootstrap citus cluster on kubernetes for now

@lfittl I would love to have an easy way to bootstrap citus cluster on Kubernetes as e.g. youtube vitess does for mysql http://vitess.io/getting-started/