From c2472dfa4f516ef05fb22f853ebd5e942cd8d0c7 Mon Sep 17 00:00:00 2001 From: Stefan Saasen Date: Thu, 17 Mar 2016 13:53:33 +1100 Subject: [PATCH 1/3] [Hello World]: Prefix 'docker push' with gcloud command In order to push to the Google Container Registry the `glcoud` command should be used as per https://cloud.google.com/container-registry/docs/#pushing_to_the_registry --- docs/hellonode.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/hellonode.md b/docs/hellonode.md index 9348e38726..0a8593233b 100755 --- a/docs/hellonode.md +++ b/docs/hellonode.md @@ -108,7 +108,7 @@ $ docker stop 2c66d0efcbd4 Now that the image works as intended and is all tagged with your `PROJECT_ID`, we can push it to the [Google Container Registry](https://cloud.google.com/tools/container-registry/), a private repository for your Docker images accessible from every Google Cloud project (but also from outside Google Cloud Platform) : ```shell -docker push gcr.io/PROJECT_ID/hello-node:v1 +gcloud docker push gcr.io/PROJECT_ID/hello-node:v1 ``` If all goes well, you should be able to see the container image listed in the console: *Compute > Container Engine > Container Registry*. We now have a project-wide Docker image available which Kubernetes can access and orchestrate. From 5387c494253fb0cf86cd92f16d4f104527c1ecba Mon Sep 17 00:00:00 2001 From: Stefan Saasen Date: Thu, 17 Mar 2016 15:17:52 +1100 Subject: [PATCH 2/3] [Hello World]: Link to kubectl/gcloud configuration documentation --- docs/hellonode.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/hellonode.md b/docs/hellonode.md index 0a8593233b..6b619cc5c8 100755 --- a/docs/hellonode.md +++ b/docs/hellonode.md @@ -124,7 +124,7 @@ Create a cluster via the Console: *Compute > Container Engine > Container Cluste ![image](/images/hellonode/image_11.png) -It’s now time to deploy your own containerized application to the Kubernetes cluster! +It’s now time to deploy your own containerized application to the Kubernetes cluster! Please ensure that you have [configured](https://cloud.google.com/container-engine/docs/before-you-begin#optional_set_gcloud_defaults) `kubectl` to use the cluster you just created. ## Create your pod From e3840a69aa9214b36b93c720c9e0092d470c94d1 Mon Sep 17 00:00:00 2001 From: Stefan Saasen Date: Thu, 17 Mar 2016 15:24:29 +1100 Subject: [PATCH 3/3] [Hello World]: Don't use the deprecated --create-external-load-balancer flag --- docs/hellonode.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/hellonode.md b/docs/hellonode.md index 6b619cc5c8..46097a58cb 100755 --- a/docs/hellonode.md +++ b/docs/hellonode.md @@ -156,7 +156,7 @@ At this point you should have our container running under the control of Kuberne By default, the pod is only accessible by its internal IP within the Kubernetes cluster. In order to make the `hello-node` container accessible from outside the kubernetes virtual network, you have to expose the pod as a kubernetes service. -From our development machine we can expose the pod with the `kubectl` expose command and the `--create-external-load-balancer=true` flag which creates an external IP to accept traffic: +From our development machine we can expose the pod with the `kubectl` expose command and the `--type="LoadBalancer"` flag which creates an external IP to accept traffic: ```shell kubectl expose rc hello-node --type="LoadBalancer"