diff --git a/docs/content/preview/deploy/kubernetes/single-zone/gke/helm-chart.md b/docs/content/preview/deploy/kubernetes/single-zone/gke/helm-chart.md index e1f6a28fd160..8699fb17120b 100644 --- a/docs/content/preview/deploy/kubernetes/single-zone/gke/helm-chart.md +++ b/docs/content/preview/deploy/kubernetes/single-zone/gke/helm-chart.md @@ -85,12 +85,14 @@ The following steps show how to meet these prerequisites: ## Create a GKE cluster -Create a Kubernetes cluster by running the following command: +Create a private Kubernetes cluster by running the following command. ```sh -gcloud container clusters create yugabyte --machine-type=n1-standard-8 +gcloud container clusters create cluster_name --enable-private-nodes --machine-type=n1-standard-8 ``` +Note that you must set up Cloud NAT for a private Kubernetes cluster in Google Cloud to ensure that your cluster can access the internet while its nodes do not have public IP addresses. Refer to [Configuring Private Google Access and Cloud NAT in Google Cloud Platform (GCP)](https://kloudkraft.medium.com/configuring-private-google-access-and-cloud-nat-in-google-cloud-platform-gcp-3c4406b590b3). + As stated in [Prerequisites](#prerequisites), the default configuration in the YugabyteDB Helm chart requires Kubernetes nodes to have a total of 12 CPU cores and 45 GB RAM allocated to YugabyteDB. This can be three nodes with 4 CPU cores and 15 GB RAM allocated to YugabyteDB. The smallest Google Cloud machine type that meets this requirement is `n1-standard-8` which has 8 CPU cores and 30GB RAM. ## Create a YugabyteDB cluster diff --git a/docs/content/preview/deploy/kubernetes/single-zone/gke/statefulset-yaml-local-ssd.md b/docs/content/preview/deploy/kubernetes/single-zone/gke/statefulset-yaml-local-ssd.md index d54abb27a596..d59a16893cfc 100644 --- a/docs/content/preview/deploy/kubernetes/single-zone/gke/statefulset-yaml-local-ssd.md +++ b/docs/content/preview/deploy/kubernetes/single-zone/gke/statefulset-yaml-local-ssd.md @@ -70,12 +70,14 @@ Each cluster brings up three nodes each of the type `n1-standard-1` for the Kube ... ``` -- Create a Kubernetes cluster on GKE by running the following in order to create a cluster in the desired zone: +- Create a private Kubernetes cluster on GKE in the desired zone by running the following. ```sh - gcloud container clusters create yugabyte --zone us-west1-b + gcloud container clusters create cluster_name --enable-private-nodes --zone us-west1-b ``` + Note that you must set up Cloud NAT for a private Kubernetes cluster in Google Cloud to ensure that your cluster can access the internet while its nodes do not have public IP addresses. Refer to [Configuring Private Google Access and Cloud NAT in Google Cloud Platform (GCP)](https://kloudkraft.medium.com/configuring-private-google-access-and-cloud-nat-in-google-cloud-platform-gcp-3c4406b590b3). + - List the available cluster by running the following command: ```sh diff --git a/docs/content/preview/deploy/kubernetes/single-zone/gke/statefulset-yaml.md b/docs/content/preview/deploy/kubernetes/single-zone/gke/statefulset-yaml.md index f001525fd4f1..7c1f234fc2a7 100644 --- a/docs/content/preview/deploy/kubernetes/single-zone/gke/statefulset-yaml.md +++ b/docs/content/preview/deploy/kubernetes/single-zone/gke/statefulset-yaml.md @@ -35,7 +35,6 @@ type: docs - ## Prerequisites Before starting deployment, perform the following: @@ -64,12 +63,14 @@ Before starting deployment, perform the following: ## Create a GKE cluster -Create a Kubernetes cluster by running the following command. +Create a private Kubernetes cluster using the following command. ```sh -gcloud container clusters create yugabyte +gcloud container clusters create cluster_name --enable-private-nodes ``` +Note that you must set up Cloud NAT for a private Kubernetes cluster in Google Cloud to ensure that your cluster can access the internet while its nodes do not have public IP addresses. Refer to [Configuring Private Google Access and Cloud NAT in Google Cloud Platform (GCP)](https://kloudkraft.medium.com/configuring-private-google-access-and-cloud-nat-in-google-cloud-platform-gcp-3c4406b590b3). + ## Create a YugabyteDB cluster Create a YugabyteDB cluster by running the following command: diff --git a/docs/content/stable/deploy/kubernetes/single-zone/gke/helm-chart.md b/docs/content/stable/deploy/kubernetes/single-zone/gke/helm-chart.md index 3f247fe9af0e..b118b05bd281 100644 --- a/docs/content/stable/deploy/kubernetes/single-zone/gke/helm-chart.md +++ b/docs/content/stable/deploy/kubernetes/single-zone/gke/helm-chart.md @@ -82,12 +82,14 @@ The following steps show how to meet these prerequisites: ## Create a GKE cluster -Create a Kubernetes cluster by running the following command: +Create a private Kubernetes cluster by running the following command. ```sh -gcloud container clusters create yugabyte --machine-type=n1-standard-8 +gcloud container clusters create cluster_name --enable-private-nodes --machine-type=n1-standard-8 ``` +Note that you must set up Cloud NAT for a private Kubernetes cluster in Google Cloud to ensure that your cluster can access the internet while its nodes do not have public IP addresses. Refer to [Configuring Private Google Access and Cloud NAT in Google Cloud Platform (GCP)](https://kloudkraft.medium.com/configuring-private-google-access-and-cloud-nat-in-google-cloud-platform-gcp-3c4406b590b3). + As stated in [Prerequisites](#prerequisites), the default configuration in the YugabyteDB Helm chart requires Kubernetes nodes to have a total of 12 CPU cores and 45 GB RAM allocated to YugabyteDB. This can be three nodes with 4 CPU cores and 15 GB RAM allocated to YugabyteDB. The smallest Google Cloud machine type that meets this requirement is `n1-standard-8` which has 8 CPU cores and 30GB RAM. ## Create a YugabyteDB cluster diff --git a/docs/content/stable/deploy/kubernetes/single-zone/gke/statefulset-yaml-local-ssd.md b/docs/content/stable/deploy/kubernetes/single-zone/gke/statefulset-yaml-local-ssd.md index b4a75a5042a9..bb6d3cf7a6eb 100644 --- a/docs/content/stable/deploy/kubernetes/single-zone/gke/statefulset-yaml-local-ssd.md +++ b/docs/content/stable/deploy/kubernetes/single-zone/gke/statefulset-yaml-local-ssd.md @@ -68,12 +68,14 @@ Each cluster brings up three nodes each of the type `n1-standard-1` for the Kube ... ``` -- Create a Kubernetes cluster on GKE by running the following in order to create a cluster in the desired zone: +- Create a private Kubernetes cluster on GKE in the desired zone by running the following. ```sh - gcloud container clusters create yugabyte --zone us-west1-b + gcloud container clusters create cluster_name --enable-private-nodes --zone us-west1-b ``` + Note that you must set up Cloud NAT for a private Kubernetes cluster in Google Cloud to ensure that your cluster can access the internet while its nodes do not have public IP addresses. Refer to [Configuring Private Google Access and Cloud NAT in Google Cloud Platform (GCP)](https://kloudkraft.medium.com/configuring-private-google-access-and-cloud-nat-in-google-cloud-platform-gcp-3c4406b590b3). + - List the available cluster by running the following command: ```sh diff --git a/docs/content/stable/deploy/kubernetes/single-zone/gke/statefulset-yaml.md b/docs/content/stable/deploy/kubernetes/single-zone/gke/statefulset-yaml.md index ef31ce7cca35..850bb6fa9d11 100644 --- a/docs/content/stable/deploy/kubernetes/single-zone/gke/statefulset-yaml.md +++ b/docs/content/stable/deploy/kubernetes/single-zone/gke/statefulset-yaml.md @@ -62,12 +62,14 @@ Before starting deployment, perform the following: ## Create a GKE cluster -Create a Kubernetes cluster by running the following command. +Create a private Kubernetes cluster using the following command. ```sh -gcloud container clusters create yugabyte +gcloud container clusters create cluster_name --enable-private-nodes ``` +Note that you must set up Cloud NAT for a private Kubernetes cluster in Google Cloud to ensure that your cluster can access the internet while its nodes do not have public IP addresses. Refer to [Configuring Private Google Access and Cloud NAT in Google Cloud Platform (GCP)](https://kloudkraft.medium.com/configuring-private-google-access-and-cloud-nat-in-google-cloud-platform-gcp-3c4406b590b3). + ## Create a YugabyteDB cluster Create a YugabyteDB cluster by running the following command: diff --git a/docs/content/v2.18/deploy/kubernetes/single-zone/gke/helm-chart.md b/docs/content/v2.18/deploy/kubernetes/single-zone/gke/helm-chart.md index 3f7db069c878..bb71d54ae097 100644 --- a/docs/content/v2.18/deploy/kubernetes/single-zone/gke/helm-chart.md +++ b/docs/content/v2.18/deploy/kubernetes/single-zone/gke/helm-chart.md @@ -82,12 +82,14 @@ The following steps show how to meet these prerequisites: ## Create a GKE cluster -Create a Kubernetes cluster by running the following command: +Create a private Kubernetes cluster using the following command. ```sh -gcloud container clusters create yugabyte --machine-type=n1-standard-8 +gcloud container clusters create cluster_name --enable-private-nodes ``` +Note that you must set up Cloud NAT for a private Kubernetes cluster in Google Cloud to ensure that your cluster can access the internet while its nodes do not have public IP addresses. Refer to [Configuring Private Google Access and Cloud NAT in Google Cloud Platform (GCP)](https://kloudkraft.medium.com/configuring-private-google-access-and-cloud-nat-in-google-cloud-platform-gcp-3c4406b590b3). + As stated in [Prerequisites](#prerequisites), the default configuration in the YugabyteDB Helm chart requires Kubernetes nodes to have a total of 12 CPU cores and 45 GB RAM allocated to YugabyteDB. This can be three nodes with 4 CPU cores and 15 GB RAM allocated to YugabyteDB. The smallest Google Cloud machine type that meets this requirement is `n1-standard-8` which has 8 CPU cores and 30GB RAM. ## Create a YugabyteDB cluster diff --git a/docs/content/v2.18/deploy/kubernetes/single-zone/gke/statefulset-yaml-local-ssd.md b/docs/content/v2.18/deploy/kubernetes/single-zone/gke/statefulset-yaml-local-ssd.md index dfdd7e8ea018..92774819ece5 100644 --- a/docs/content/v2.18/deploy/kubernetes/single-zone/gke/statefulset-yaml-local-ssd.md +++ b/docs/content/v2.18/deploy/kubernetes/single-zone/gke/statefulset-yaml-local-ssd.md @@ -68,12 +68,14 @@ Each cluster brings up three nodes each of the type `n1-standard-1` for the Kube ... ``` -- Create a Kubernetes cluster on GKE by running the following in order to create a cluster in the desired zone: +- Create a private Kubernetes cluster using the following command. ```sh - gcloud container clusters create yugabyte --zone us-west1-b + gcloud container clusters create cluster_name --enable-private-nodes ``` + Note that you must set up Cloud NAT for a private Kubernetes cluster in Google Cloud to ensure that your cluster can access the internet while its nodes do not have public IP addresses. Refer to [Configuring Private Google Access and Cloud NAT in Google Cloud Platform (GCP)](https://kloudkraft.medium.com/configuring-private-google-access-and-cloud-nat-in-google-cloud-platform-gcp-3c4406b590b3). + - List the available cluster by running the following command: ```sh diff --git a/docs/content/v2.18/deploy/kubernetes/single-zone/gke/statefulset-yaml.md b/docs/content/v2.18/deploy/kubernetes/single-zone/gke/statefulset-yaml.md index 0a96bb5f6d6b..f7aca6102c9b 100644 --- a/docs/content/v2.18/deploy/kubernetes/single-zone/gke/statefulset-yaml.md +++ b/docs/content/v2.18/deploy/kubernetes/single-zone/gke/statefulset-yaml.md @@ -62,12 +62,14 @@ Before starting deployment, perform the following: ## Create a GKE cluster -Create a Kubernetes cluster by running the following command. +Create a private Kubernetes cluster using the following command. ```sh -gcloud container clusters create yugabyte +gcloud container clusters create cluster_name --enable-private-nodes ``` +Note that you must set up Cloud NAT for a private Kubernetes cluster in Google Cloud to ensure that your cluster can access the internet while its nodes do not have public IP addresses. Refer to [Configuring Private Google Access and Cloud NAT in Google Cloud Platform (GCP)](https://kloudkraft.medium.com/configuring-private-google-access-and-cloud-nat-in-google-cloud-platform-gcp-3c4406b590b3). + ## Create a YugabyteDB cluster Create a YugabyteDB cluster by running the following command: diff --git a/docs/content/v2.20/deploy/kubernetes/single-zone/gke/helm-chart.md b/docs/content/v2.20/deploy/kubernetes/single-zone/gke/helm-chart.md index f7b16d6bd499..18a427c58460 100644 --- a/docs/content/v2.20/deploy/kubernetes/single-zone/gke/helm-chart.md +++ b/docs/content/v2.20/deploy/kubernetes/single-zone/gke/helm-chart.md @@ -82,12 +82,14 @@ The following steps show how to meet these prerequisites: ## Create a GKE cluster -Create a Kubernetes cluster by running the following command: +Create a private Kubernetes cluster using the following command. ```sh -gcloud container clusters create yugabyte --machine-type=n1-standard-8 +gcloud container clusters create cluster_name --enable-private-nodes ``` +Note that you must set up Cloud NAT for a private Kubernetes cluster in Google Cloud to ensure that your cluster can access the internet while its nodes do not have public IP addresses. Refer to [Configuring Private Google Access and Cloud NAT in Google Cloud Platform (GCP)](https://kloudkraft.medium.com/configuring-private-google-access-and-cloud-nat-in-google-cloud-platform-gcp-3c4406b590b3). + As stated in [Prerequisites](#prerequisites), the default configuration in the YugabyteDB Helm chart requires Kubernetes nodes to have a total of 12 CPU cores and 45 GB RAM allocated to YugabyteDB. This can be three nodes with 4 CPU cores and 15 GB RAM allocated to YugabyteDB. The smallest Google Cloud machine type that meets this requirement is `n1-standard-8` which has 8 CPU cores and 30GB RAM. ## Create a YugabyteDB cluster diff --git a/docs/content/v2.20/deploy/kubernetes/single-zone/gke/statefulset-yaml-local-ssd.md b/docs/content/v2.20/deploy/kubernetes/single-zone/gke/statefulset-yaml-local-ssd.md index a5d582852ad5..254a271c1fed 100644 --- a/docs/content/v2.20/deploy/kubernetes/single-zone/gke/statefulset-yaml-local-ssd.md +++ b/docs/content/v2.20/deploy/kubernetes/single-zone/gke/statefulset-yaml-local-ssd.md @@ -68,12 +68,14 @@ Each cluster brings up three nodes each of the type `n1-standard-1` for the Kube ... ``` -- Create a Kubernetes cluster on GKE by running the following in order to create a cluster in the desired zone: +- Create a private Kubernetes cluster using the following command. ```sh - gcloud container clusters create yugabyte --zone us-west1-b + gcloud container clusters create cluster_name --enable-private-nodes ``` + Note that you must set up Cloud NAT for a private Kubernetes cluster in Google Cloud to ensure that your cluster can access the internet while its nodes do not have public IP addresses. Refer to [Configuring Private Google Access and Cloud NAT in Google Cloud Platform (GCP)](https://kloudkraft.medium.com/configuring-private-google-access-and-cloud-nat-in-google-cloud-platform-gcp-3c4406b590b3). + - List the available cluster by running the following command: ```sh diff --git a/docs/content/v2.20/deploy/kubernetes/single-zone/gke/statefulset-yaml.md b/docs/content/v2.20/deploy/kubernetes/single-zone/gke/statefulset-yaml.md index 9ddd391e41b5..3a93fa421acd 100644 --- a/docs/content/v2.20/deploy/kubernetes/single-zone/gke/statefulset-yaml.md +++ b/docs/content/v2.20/deploy/kubernetes/single-zone/gke/statefulset-yaml.md @@ -62,12 +62,14 @@ Before starting deployment, perform the following: ## Create a GKE cluster -Create a Kubernetes cluster by running the following command. +Create a private Kubernetes cluster using the following command. ```sh -gcloud container clusters create yugabyte +gcloud container clusters create cluster_name --enable-private-nodes ``` +Note that you must set up Cloud NAT for a private Kubernetes cluster in Google Cloud to ensure that your cluster can access the internet while its nodes do not have public IP addresses. Refer to [Configuring Private Google Access and Cloud NAT in Google Cloud Platform (GCP)](https://kloudkraft.medium.com/configuring-private-google-access-and-cloud-nat-in-google-cloud-platform-gcp-3c4406b590b3). + ## Create a YugabyteDB cluster Create a YugabyteDB cluster by running the following command: