"Deploying Scylla on GKE" should create nodes of ScyllaDB pool in multiple zones

[rzetelskik]

To align with Deploying Scylla on EKS guide and to promote good practices, the GKE guide should describe the commands which would deploy the ScyllaDB node pool instances in different zones, instead of multiple instances in the same zone. Same goes for the TLDR script. This can be achieved by using --location and --node-locations flags of gcloud container command.

       --location=LOCATION
          Compute zone or region (e.g. us-central1-a or us-central1) for the
          cluster.

     --node-locations=ZONE,[ZONE,...]
        The set of zones in which the specified node footprint should be
        replicated. All zones must be in the same region as the cluster's
        master(s), specified by the -location, --zone, or --region flag.
        Additionally, for zonal clusters, --node-locations must contain the
        cluster's primary zone. If not specified, all nodes will be in the
        cluster's primary zone (for zonal clusters) or spread across three
        randomly chosen zones within the cluster's region (for regional
        clusters).

        Note that NUM_NODES nodes will be created in each zone, such that if
        you specify --num-nodes=4 and choose two locations, 8 nodes will be
        created.

        Multiple locations can be specified, separated by commas. For example:

            $ gcloud container clusters create example-cluster \
                --location us-central1-a \
                --node-locations us-central1-a,us-central1-b

For example, the following command creates a regional node pool with 3 nodes spread across us-east1-b, us-east1-c and us-east1-d.

gcloud container node-pools create "scylla-pool" \
--cluster scylladb-us-east1 \
--machine-type "n1-standard-8" \
--num-nodes "1" \
--disk-type "pd-ssd" --disk-size "20" \
--local-nvme-ssd-block count="8" \
--node-taints role=scylla-clusters:NoSchedule \
--node-labels scylla.scylladb.com/node-type=scylla \
--image-type "UBUNTU_CONTAINERD" \
--no-enable-autoupgrade \
--no-enable-autorepair \
--location us-east1 \
--node-locations us-east1-b,us-east1-c,us-east1-d

[rzetelskik]

This actually applies to the default pool as well

[scylla-operator-bot[bot]]

The Scylla Operator project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 30d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out

/lifecycle stale

[tnozicka]

/remove-lifecycle stale /triage accepted