From b39b1ca2cb036a273c058e144b34ff62190dfa9a Mon Sep 17 00:00:00 2001 From: AdamDang Date: Sun, 13 May 2018 21:38:06 +0800 Subject: [PATCH 1/3] Correct all the word "cluster" to be in lowercase In the main text of this doc, We can see "cluster" "Cluster" "clusters" "Clusters". My suggestion: in lowercase. --- docs/tutorial/gce.md | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/docs/tutorial/gce.md b/docs/tutorial/gce.md index 0271afeb51..75dfd24c9b 100644 --- a/docs/tutorial/gce.md +++ b/docs/tutorial/gce.md @@ -21,7 +21,7 @@ So, just create an empty bucket - you can use any name: `gsutil mb gs://kubernet # Creating our first cluster -`kops create cluster` creates the Cluster and InstanceGroup objects you'll be working with in kops: +`kops create cluster` creates the cluster and InstanceGroup objects you'll be working with in kops: ``` PROJECT=`gcloud config get-value project` @@ -40,14 +40,14 @@ simple.k8s.local gce us-central1-a -This shows that you have one Cluster configured, named `simple.k8s.local`. The Cluster holds the cluster-wide configuration for +This shows that you have one cluster configured, named `simple.k8s.local`. The cluster holds the cluster-wide configuration for a kubernetes cluster - things like the kubernetes version, and the authorization policy in use. The `kops` tool should feel a lot like `kubectl` - kops uses the same API machinery as kubernetes, so it should behave similarly, although now you are managing kubernetes clusters, instead of managing objects on a kubernetes cluster. -You can see the details of your Cluster by doing: +You can see the details of your cluster by doing: `> kops get cluster --state gs://kubernetes-clusters/ simple.k8s.local -oyaml` ``` @@ -113,7 +113,7 @@ which then are registered in kubernetes as Nodes. You have multiple InstanceGro of instances / Nodes - in our simple example we have one for our master (which only has a single member), and one for our nodes (and we have two nodes configured). -We'll see a lot more of Clusters and InstanceGroups as we use kops to reconfigure clusters. But let's get +We'll see a lot more of clusters and InstanceGroups as we use kops to reconfigure clusters. But let's get on with our first cluster. # Export KOPS_STATE_STORE @@ -129,7 +129,7 @@ You can also put this in your `~/.bashrc` or similar. # Creating a cluster -`kops create cluster` created the Cluster & InstanceGroup objects in our state store, +`kops create cluster` created the cluster & InstanceGroup objects in our state store, but didn't actually create any instances or other cloud objects in GCE. To do that, we'll use `kops update cluster`. From be1434e14a3c3e509ef1c1fd937db2c83d050135 Mon Sep 17 00:00:00 2001 From: AdamDang Date: Tue, 3 Jul 2018 14:37:58 +0800 Subject: [PATCH 2/3] Update gce.md --- docs/tutorial/gce.md | 14 +++++++------- 1 file changed, 7 insertions(+), 7 deletions(-) diff --git a/docs/tutorial/gce.md b/docs/tutorial/gce.md index 75dfd24c9b..0e728a27e9 100644 --- a/docs/tutorial/gce.md +++ b/docs/tutorial/gce.md @@ -13,7 +13,7 @@ You'll also need to [configure default credentials](https://developers.google.co # Creating a state store -kops needs a state store, to hold the configuration for your clusters. The simplest configuration +kops needs a state store, to hold the configuration for your Clusters. The simplest configuration for Google Cloud is to store it in a Google Cloud Storage bucket in the same account, so that's how we'll start. @@ -21,7 +21,7 @@ So, just create an empty bucket - you can use any name: `gsutil mb gs://kubernet # Creating our first cluster -`kops create cluster` creates the cluster and InstanceGroup objects you'll be working with in kops: +`kops create cluster` creates the Cluster object and InstanceGroup object you'll be working with in kops: ``` PROJECT=`gcloud config get-value project` @@ -29,7 +29,7 @@ export KOPS_FEATURE_FLAGS=AlphaAllowGCE # to unlock the GCE features kops create cluster simple.k8s.local --zones us-central1-a --state gs://kubernetes-clusters/ --project=${PROJECT} ``` -You can now list the clusters in your kops state store (the GCS bucket we created): +You can now list the Cluster objects in your kops state store (the GCS bucket we created): `kops get cluster --state gs://kubernetes-clusters/` @@ -40,14 +40,14 @@ simple.k8s.local gce us-central1-a -This shows that you have one cluster configured, named `simple.k8s.local`. The cluster holds the cluster-wide configuration for +This shows that you have one Cluster object configured, named `simple.k8s.local`. The cluster holds the cluster-wide configuration for a kubernetes cluster - things like the kubernetes version, and the authorization policy in use. The `kops` tool should feel a lot like `kubectl` - kops uses the same API machinery as kubernetes, so it should behave similarly, although now you are managing kubernetes clusters, instead of managing objects on a kubernetes cluster. -You can see the details of your cluster by doing: +You can see the details of your Cluster object by doing: `> kops get cluster --state gs://kubernetes-clusters/ simple.k8s.local -oyaml` ``` @@ -113,7 +113,7 @@ which then are registered in kubernetes as Nodes. You have multiple InstanceGro of instances / Nodes - in our simple example we have one for our master (which only has a single member), and one for our nodes (and we have two nodes configured). -We'll see a lot more of clusters and InstanceGroups as we use kops to reconfigure clusters. But let's get +We'll see a lot more of Cluster objects and InstanceGroups as we use kops to reconfigure clusters. But let's get on with our first cluster. # Export KOPS_STATE_STORE @@ -129,7 +129,7 @@ You can also put this in your `~/.bashrc` or similar. # Creating a cluster -`kops create cluster` created the cluster & InstanceGroup objects in our state store, +`kops create cluster` created the Cluster object & InstanceGroup object in our state store, but didn't actually create any instances or other cloud objects in GCE. To do that, we'll use `kops update cluster`. From 6a7f3cab5596ff5b8ebbf0745c3b9eb05c95e1b1 Mon Sep 17 00:00:00 2001 From: AdamDang Date: Tue, 3 Jul 2018 14:39:24 +0800 Subject: [PATCH 3/3] Update gce.md --- docs/tutorial/gce.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/tutorial/gce.md b/docs/tutorial/gce.md index 0e728a27e9..3843c79777 100644 --- a/docs/tutorial/gce.md +++ b/docs/tutorial/gce.md @@ -13,7 +13,7 @@ You'll also need to [configure default credentials](https://developers.google.co # Creating a state store -kops needs a state store, to hold the configuration for your Clusters. The simplest configuration +kops needs a state store, to hold the configuration for your clusters. The simplest configuration for Google Cloud is to store it in a Google Cloud Storage bucket in the same account, so that's how we'll start.