Replaced (or defined first instance of) GKE/GCE with Google Container Engine/Google Compute Engine

Fixes #10354
This commit is contained in:
RichieEscarez
2015-06-26 12:13:43 -07:00
parent ffb846a284
commit 899145da10
21 changed files with 34 additions and 34 deletions

View File

@@ -56,7 +56,7 @@ If you want more control over the upgrading process, you may use the following w
`kubectl update nodes $NODENAME --patch='{"apiVersion": "v1", "spec": {"unschedulable": false}}'`.
If you deleted the node's VM instance and created a new one, then a new schedulable node resource will
be created automatically when you create a new VM instance (if you're using a cloud provider that supports
node discovery; currently this is only GCE, not including CoreOS on GCE using kube-register). See [Node](node.md).
node discovery; currently this is only Google Compute Engine, not including CoreOS on Google Compute Engine using kube-register). See [Node](node.md).
[![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/docs/cluster_management.md?pixel)]()