Skip to content

Commit

Permalink
Merge pull request #1591 from rzetelskik/gke-docs-raw-block-v1.11
Browse files Browse the repository at this point in the history
[v1.11] Update outdated hyperlink to GKE's raw block devices docs in GKE docs
  • Loading branch information
scylla-operator-bot[bot] authored Nov 23, 2023
2 parents ca030a9 + 133bcdd commit aed9c6a
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion docs/source/gke.md
Original file line number Diff line number Diff line change
Expand Up @@ -90,7 +90,7 @@ Then we'll create a GKE cluster with the following:
--no-enable-autorepair
```
3. A NodePool of 4 `n1-standard-32` Nodes, where the Scylla Pods will be deployed. Each of these Nodes has 8 local NVMe SSDs attached, which are provided as [raw block devices](https://cloud.google.com/kubernetes-engine/docs/how-to/persistent-volumes/local-ssd#raw-block). It is important to disable `autoupgrade` and `autorepair`. Automatic cluster upgrade or node repair has a hard timeout after which it no longer respect PDBs and force deletes the Compute Engine instances, which also deletes all data on the local SSDs. At this point, it's better to handle upgrades manually, with more control over the process and error handling.
3. A NodePool of 4 `n1-standard-32` Nodes, where the Scylla Pods will be deployed. Each of these Nodes has 8 local NVMe SSDs attached, which are provided as [raw block devices](https://cloud.google.com/kubernetes-engine/docs/concepts/local-ssd#block). It is important to disable `autoupgrade` and `autorepair`. Automatic cluster upgrade or node repair has a hard timeout after which it no longer respect PDBs and force deletes the Compute Engine instances, which also deletes all data on the local SSDs. At this point, it's better to handle upgrades manually, with more control over the process and error handling.
```
gcloud container \
node-pools create "scylla-pool" \
Expand Down

0 comments on commit aed9c6a

Please sign in to comment.