{"id":639,"date":"2017-10-15T08:31:57","date_gmt":"2017-10-15T08:31:57","guid":{"rendered":"http:\/\/tuxlabs.com\/?p=639"},"modified":"2020-01-04T17:09:08","modified_gmt":"2020-01-04T17:09:08","slug":"setting-up-kubernetes-to-manage-containers-on-the-google-cloud-platform","status":"publish","type":"post","link":"https:\/\/tuxlabs.com\/?p=639","title":{"rendered":"Setting up Kubernetes to manage containers on the Google Cloud Platform"},"content":{"rendered":"

\"\"<\/a><\/p>\n

These days the pace of innovation in DevOps can leave you feeling like you’re jogging on a treadmill programmed to run faster than Usain Bolt<\/a>. Mastery requires hours of practice and the last decade in DevOps has not allowed for it. Before gaining 10 years of experience running virtual machines using VmWare in private data-centers, private cloud software like Openstack and Cloudstack came along, and just when you and your team painfully achieved a stable install you were told running virtual machines in public clouds like AWS<\/a>, GCP<\/a>, and Azure<\/a> is the way forward. By the time you got there it was time to switch to containers, and before you can fully appreciate those, server-less functions are on the horizon, but I digress. If you want to know more about server-less functions, see my previous article on AWS Lambda<\/a>. Instead, this article will focus on running Docker containers<\/a> inside of a Kubernetes<\/a> cluster on Google’s Cloud Platform<\/a>.<\/p>\n

Linux Containers<\/a>, which were recently popularized by Docker<\/a> need something to help manage them and while there are many choices, Kubernetes<\/a> the open-sourced container management system from Google is the undisputed king at this time. Given that Kubernetes was started by Google, it should be expected that the easiest way to install it is using Google’s Cloud Platform (GCP). However, Openshift<\/a> from Redhat<\/a> also provides a nice batteries included abstraction if you need to get up and running quickly as well as kops<\/a>.<\/p>\n

Pre-Requisites<\/h3>\n

The main pre-requisites you need for this article is a Google Cloud Platform account<\/a> and installing the gcloud<\/a> utility via the SDK<\/a>.<\/p>\n

In addition, you need some form of a computer with Internet connectivity, some typing skills, a brain that can read, and a determination to finish…For now I will give you the benefit of the doubt and assume you have all of these. It is also nice to have your beverage of choice while you do this, a fine tea, ice cold beer, or glass of wine will work, but for Cancer’s sake please skip the sugar.<\/p>\n

Here is where I would normally insert a link to facts on sugar and Cancer’s link, but I literally just learned I would be spreading rumors<\/a>… Fine drink your Kool-Aid, but don’t blame me for your calories.<\/p><\/blockquote>\n

The Build Out of our Self Healing IRC Server Hosting Containers<\/h3>\n

I lied dude, IRC<\/a> is so 1995 and unfortunately, ICQ’s<\/a> been dead and Slack<\/a> won’t let me host their sexy chat application with game like spirit and better jokes than Kevin Heart<\/a>. So…sorry to excite you… but I guess I will fallback to the docs<\/a> here and install Nginx<\/a> like us newb’s<\/a> are supposed to.<\/p>\n

Numero Uno (Step 1 dude)<\/h3>\n

As part of the installation of the gcloud \/ SDK<\/a> you should have ran gcloud init, which requires you to login with your Google account via a web browser.<\/p>\n

You must log in to continue. Would you like to log in (Y\/n)?  Y\n\nYour browser has been opened to visit:\n\n    https:\/\/accounts.google.com\/o\/oauth2\/auth?redirect_uri=http%3A%2F%2Flocalhost%3A8085%2F&prompt=select_account&response_type=code&client_id=32555940559.apps.googleusercontent.com&scope=https%3A%2F%2Fwww.googleapis.com%2Fauth%2Fuserinfo.email+https%3A%2F%2Fwww.googleapis.com%2Fauth%2Fcloud-platform+https%3A%2F%2Fwww.googleapis.com%2Fauth%2Fappengine.admin+https%3A%2F%2Fwww.googleapis.com%2Fauth%2Fcompute+https%3A%2F%2Fwww.googleapis.com%2Fauth%2Faccounts.reauth&access_type=offline\n\n\nYou are logged in as: [tuxninja@tuxlabs.com].\n\nThis account has no projects.\n\nWould you like to create one? (Y\/n)?  Y\n<\/pre>\n
After clicking allow in your browser you will be logged in…and asked about creating an initial Project. Say yes (type Y and hit enter).<\/p>\n
Enter a Project ID. Note that a Project ID CANNOT be changed later.\nProject IDs must be 6-30 characters (lowercase ASCII, digits, or\nhyphens) in length and start with a lowercase letter. tuxlabsdemo\nYour current project has been set to: [tuxlabsdemo].\n\nNot setting default zone\/region (this feature makes it easier to use\n[gcloud compute] by setting an appropriate default value for the\n--zone and --region flag).\nSee https:\/\/cloud.google.com\/compute\/docs\/gcloud-compute section on how to set\ndefault compute region and zone manually. If you would like [gcloud init] to be\nable to do this for you the next time you run it, make sure the\nCompute Engine API is enabled for your project on the\nhttps:\/\/console.developers.google.com\/apis page.\n\nYour Google Cloud SDK is configured and ready to use!\n<\/pre>\n
Sweet your Project is now created. In order to use the Google Cloud API’s you must first enable access by visiting https:\/\/console.developers.google.com\/apis\/api\/replicapool.googleapis.com\/overview<\/a> and clicking enable.<\/p>\n
\"\"<\/a><\/p>\n
That will take a minute. Once completed you will be able to run gcloud commands against your Project. We can set the default region for our project like so:<\/p>\n
tuxninja@tldev1:~\/google-cloud-sdk$ gcloud compute project-info add-metadata --metadata google-compute-default-region=us-west1\nUpdated [https:\/\/www.googleapis.com\/compute\/v1\/projects\/tuxlabsdemo].\ntuxninja@tldev1:~\/google-cloud-sdk$ \n<\/pre>\n
If you get an error here, stop being cheap and link your project to your billing account in the console.<\/p>\n
Additionally, we want to set the default region\/zone for gcloud commands like so:<\/p>\n
tuxninja@tldev1:~$ gcloud config set compute\/region us-west1\nUpdated property [compute\/region].\ntuxninja@tldev1:~$ gcloud config set compute\/zone us-west1-a\nUpdated property [compute\/zone].\ntuxninja@tldev1:~$ \n<\/pre>\n
Numero Dos Equis<\/a><\/h3>\n
We need to install kubectl so we can interact with Kubernetes.<\/p>\n
tuxninja@tldev1:~$ gcloud components install kubectl\n\n\nYour current Cloud SDK version is: 175.0.0\nInstalling components from version: 175.0.0\n\n\u250c\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2510\n\u2502               These components will be installed.                \u2502\n\u251c\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u252c\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u252c\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2524\n\u2502         Name        \u2502       Version       \u2502         Size         \u2502\n\u251c\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u253c\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u253c\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2524\n\u2502 kubectl             \u2502               1.7.6 \u2502             16.0 MiB \u2502\n\u2502 kubectl             \u2502                     \u2502                      \u2502\n\u2514\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2534\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2534\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2518\n\nFor the latest full release notes, please visit:\n  https:\/\/cloud.google.com\/sdk\/release_notes\n\nDo you want to continue (Y\/n)?  Y\n\n\u2554\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2557\n\u2560\u2550 Creating update staging area                             \u2550\u2563\n\u2560\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2563\n\u2560\u2550 Installing: kubectl                                      \u2550\u2563\n\u2560\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2563\n\u2560\u2550 Installing: kubectl                                      \u2550\u2563\n\u2560\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2563\n\u2560\u2550 Creating backup and activating new installation          \u2550\u2563\n\u255a\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u255d\n\nPerforming post processing steps...done.                                                                                                                      \n\nUpdate done!\n\ntuxninja@tldev1:~$ \n<\/pre>\n
Once that is done, quickly realize someone spent an obscene amount of time making that install as pretty as it was without using ncurses<\/a>. Shout out to that geek.<\/p>\n
Numero Tres Deliquentes<\/a><\/h3>\n
Time to create our Kubernetes cluster. Run this command and “it’s going to be LEGEND<\/strong>….Wait for it<\/strong>….<\/p>\n
tuxninja@tldev1:~$ gcloud container clusters create tuxlabs-kubernetes                           \nCreating cluster tuxlabs-kubernetes...done.                                                   \nCreated [https:\/\/container.googleapis.com\/v1\/projects\/tuxlabsdemo\/zones\/us-west1-a\/clusters\/tuxlabs-kubernetes].\nkubeconfig entry generated for tuxlabs-kubernetes.\nNAME                ZONE        MASTER_VERSION  MASTER_IP       MACHINE_TYPE   NODE_VERSION  NUM_NODES  STATUS\ntuxlabs-kubernetes  us-west1-a  1.7.6-gke.1     35.197.120.249  n1-standard-1  1.7.6         3          RUNNING\ntuxninja@tldev1:~$<\/pre>\n
And I hope you’re not lactose intolerant cause the second half of that word is DAIRY<\/a><\/strong>.” – NPH<\/p>\n
Numero (Audi) Quattro<\/a><\/h3>\n
Now you should be able to see all running Kubernetes services<\/strong> in your cluster like so:<\/p>\n
tuxninja@tldev1:~$ kubectl get --all-namespaces services\nNAMESPACE     NAME                   TYPE        CLUSTER-IP      EXTERNAL-IP   PORT(S)         AGE\ndefault       kubernetes             ClusterIP   10.19.240.1     <none>        443\/TCP         15m\nkube-system   default-http-backend   NodePort    10.19.254.83    <none>        80:31154\/TCP    14m\nkube-system   heapster               ClusterIP   10.19.247.182   <none>        80\/TCP          14m\nkube-system   kube-dns               ClusterIP   10.19.240.10    <none>        53\/UDP,53\/TCP   14m\nkube-system   kubernetes-dashboard   ClusterIP   10.19.249.188   <none>        80\/TCP          14m\ntuxninja@tldev1:~$<\/pre>\n
And we can see the pods like so:<\/strong><\/p>\n
tuxninja@tldev1:~$ kubectl get --all-namespaces pods\nNAMESPACE     NAME                                                           READY     STATUS    RESTARTS   AGE\nkube-system   event-exporter-1421584133-zlvnd                                2\/2       Running   0          16m\nkube-system   fluentd-gcp-v2.0-1nb9x                                         2\/2       Running   0          16m\nkube-system   fluentd-gcp-v2.0-bpqtv                                         2\/2       Running   0          16m\nkube-system   fluentd-gcp-v2.0-mntjl                                         2\/2       Running   0          16m\nkube-system   heapster-v1.4.2-339128277-gxh5g                                3\/3       Running   0          15m\nkube-system   kube-dns-3468831164-5nn05                                      3\/3       Running   0          15m\nkube-system   kube-dns-3468831164-wcwtg                                      3\/3       Running   0          16m\nkube-system   kube-dns-autoscaler-244676396-fnq9g                            1\/1       Running   0          16m\nkube-system   kube-proxy-gke-tuxlabs-kubernetes-default-pool-6ede7d6a-nvfg   1\/1       Running   0          16m\nkube-system   kube-proxy-gke-tuxlabs-kubernetes-default-pool-6ede7d6a-pr82   1\/1       Running   0          16m\nkube-system   kube-proxy-gke-tuxlabs-kubernetes-default-pool-6ede7d6a-w6p8   1\/1       Running   0          16m\nkube-system   kubernetes-dashboard-1265873680-gftnz                          1\/1       Running   0          16m\nkube-system   l7-default-backend-3623108927-57292                            1\/1       Running   0          16m\ntuxninja@tldev1:~$ \n<\/pre>\n
Numero Cinco (de Mayo)<\/a><\/h3>\n
You now have an active Kubernetes cluster. That is pretty sweet huh? Make sure you take the time to check out what’s running under the hood in the Google Compute Engine as well.<\/p>\n
tuxninja@tldev1:~$ gcloud compute instances list\nNAME                                               ZONE        MACHINE_TYPE   PREEMPTIBLE  INTERNAL_IP  EXTERNAL_IP     STATUS\ngke-tuxlabs-kubernetes-default-pool-6ede7d6a-nvfg  us-west1-a  n1-standard-1               10.138.0.2   35.197.94.114   RUNNING\ngke-tuxlabs-kubernetes-default-pool-6ede7d6a-pr82  us-west1-a  n1-standard-1               10.138.0.3   35.197.2.247    RUNNING\ngke-tuxlabs-kubernetes-default-pool-6ede7d6a-w6p8  us-west1-a  n1-standard-1               10.138.0.4   35.197.117.173  RUNNING\ntuxninja@tldev1:~$ \n<\/pre>\n
Ok, for our final act, I promised Nginx<\/strong><\/a>…sigh…Let’s get this over with!<\/p>\n
Step 1, create this nifty YAML file:<\/strong><\/p>\n
apiVersion: apps\/v1beta1\nkind: Deployment\nmetadata:\n  name: nginx-deployment\nspec:\n  selector:\n    matchLabels:\n      app: nginx\n  replicas: 2 # tells deployment to run 2 pods matching the template\n  template: # create pods using pod definition in this template\n    metadata:\n      # unlike pod-nginx.yaml, the name is not included in the meta data as a unique name is\n      # generated from the deployment name\n      labels:\n        app: nginx\n    spec:\n      containers:\n      - name: nginx\n        image: nginx:1.7.9\n        ports:\n        - containerPort: 80\n<\/pre>\n
Save it as deployment.yaml, then apply it!<\/strong><\/p>\n
tuxninja@tldev1:~$ kubectl apply -f deployment.yaml \ndeployment \"nginx-deployment\" created\ntuxninja@tldev1:~$<\/pre>\n
We can describe our deployment like this:<\/strong><\/p>\n
tuxninja@tldev1:~$ kubectl describe deployment nginx-deployment\nName:                   nginx-deployment\nNamespace:              default\nCreationTimestamp:      Sun, 15 Oct 2017 07:10:52 +0000\nLabels:                 app=nginx\nAnnotations:            deployment.kubernetes.io\/revision=1\n                        kubectl.kubernetes.io\/last-applied-configuration={\"apiVersion\":\"apps\/v1beta1\",\"kind\":\"Deployment\",\"metadata\":{\"annotations\":{},\"name\":\"nginx-deployment\",\"namespace\":\"default\"},\"spec\":{\"replicas\":2,\"se...\nSelector:               app=nginx\nReplicas:               2 desired | 2 updated | 2 total | 2 available | 0 unavailable\nStrategyType:           RollingUpdate\nMinReadySeconds:        0\nRollingUpdateStrategy:  25% max unavailable, 25% max surge\nPod Template:\n  Labels:  app=nginx\n  Containers:\n   nginx:\n    Image:        nginx:1.7.9\n    Port:         80\/TCP\n    Environment:  <none>\n    Mounts:       <none>\n  Volumes:        <none>\nConditions:\n  Type           Status  Reason\n  ----           ------  ------\n  Available      True    MinimumReplicasAvailable\n  Progressing    True    NewReplicaSetAvailable\nOldReplicaSets:  <none>\nNewReplicaSet:   nginx-deployment-431080787 (2\/2 replicas created)\nEvents:\n  Type    Reason             Age   From                   Message\n  ----    ------             ----  ----                   -------\n  Normal  ScalingReplicaSet  3m    deployment-controller  Scaled up replica set nginx-deployment-431080787 to 2\ntuxninja@tldev1:~$<\/pre>\n
And we can take a gander at the pods created for this deployment<\/strong><\/p>\n
tuxninja@tldev1:~$ kubectl get pods -l app=nginx\nNAME                               READY     STATUS    RESTARTS   AGE\nnginx-deployment-431080787-7131f   1\/1       Running   0          4m\nnginx-deployment-431080787-cgwn8   1\/1       Running   0          4m\ntuxninja@tldev1:~$<\/pre>\n
To see info about a specific pod run: <\/strong><\/p>\n
tuxninja@tldev1:~$ kubectl describe pod nginx-deployment-431080787-7131f\nName:           nginx-deployment-431080787-7131f\nNamespace:      default\nNode:           gke-tuxlabs-kubernetes-default-pool-6ede7d6a-nvfg\/10.138.0.2\nStart Time:     Sun, 15 Oct 2017 07:10:52 +0000\nLabels:         app=nginx\n                pod-template-hash=431080787\nAnnotations:    kubernetes.io\/created-by={\"kind\":\"SerializedReference\",\"apiVersion\":\"v1\",\"reference\":{\"kind\":\"ReplicaSet\",\"namespace\":\"default\",\"name\":\"nginx-deployment-431080787\",\"uid\":\"faa4d17b-b177-11e7-b439-42010...\n                kubernetes.io\/limit-ranger=LimitRanger plugin set: cpu request for container nginx\nStatus:         Running\nIP:             10.16.1.4\nCreated By:     ReplicaSet\/nginx-deployment-431080787\nControlled By:  ReplicaSet\/nginx-deployment-431080787\nContainers:\n  nginx:\n    Container ID:   docker:\/\/ce850ea012243e6d31e5eabfcc07aa71c33b3c1935e1ff1670282f22ac1d0907\n    Image:          nginx:1.7.9\n    Image ID:       docker-pullable:\/\/nginx@sha256:e3456c851a152494c3e4ff5fcc26f240206abac0c9d794affb40e0714846c451\n    Port:           80\/TCP\n    State:          Running\n      Started:      Sun, 15 Oct 2017 07:11:01 +0000\n    Ready:          True\n    Restart Count:  0\n    Requests:\n      cpu:        100m\n    Environment:  <none>\n    Mounts:\n      \/var\/run\/secrets\/kubernetes.io\/serviceaccount from default-token-gw047 (ro)\nConditions:\n  Type           Status\n  Initialized    True \n  Ready          True \n  PodScheduled   True \nVolumes:\n  default-token-gw047:\n    Type:        Secret (a volume populated by a Secret)\n    SecretName:  default-token-gw047\n    Optional:    false\nQoS Class:       Burstable\nNode-Selectors:  <none>\nTolerations:     node.alpha.kubernetes.io\/notReady:NoExecute for 300s\n                 node.alpha.kubernetes.io\/unreachable:NoExecute for 300s\nEvents:\n  Type    Reason                 Age   From                                                        Message\n  ----    ------                 ----  ----                                                        -------\n  Normal  Scheduled              5m    default-scheduler                                           Successfully assigned nginx-deployment-431080787-7131f to gke-tuxlabs-kubernetes-default-pool-6ede7d6a-nvfg\n  Normal  SuccessfulMountVolume  5m    kubelet, gke-tuxlabs-kubernetes-default-pool-6ede7d6a-nvfg  MountVolume.SetUp succeeded for volume \"default-token-gw047\"\n  Normal  Pulling                5m    kubelet, gke-tuxlabs-kubernetes-default-pool-6ede7d6a-nvfg  pulling image \"nginx:1.7.9\"\n  Normal  Pulled                 5m    kubelet, gke-tuxlabs-kubernetes-default-pool-6ede7d6a-nvfg  Successfully pulled image \"nginx:1.7.9\"\n  Normal  Created                5m    kubelet, gke-tuxlabs-kubernetes-default-pool-6ede7d6a-nvfg  Created container\n  Normal  Started                5m    kubelet, gke-tuxlabs-kubernetes-default-pool-6ede7d6a-nvfg  Started container\ntuxninja@tldev1:~$ \n<\/pre>\n
Finally it’s time to expose Nginx to the Internet<\/strong><\/p>\n
tuxninja@tldev1:~$ kubectl expose deployment\/nginx-deployment --port=80 --target-port=80 --name=nginx-deployment --type=LoadBalancer\nservice \"nginx-deployment\" exposed\ntuxninja@tldev1:~<\/pre>\n
Check the status of our service<\/strong><\/p>\n
tuxninja@tldev1:~$ kubectl get svc nginx-deploymentNAME               TYPE           CLUSTER-IP     EXTERNAL-IP   PORT(S)        AGE\nnginx-deployment   LoadBalancer   10.19.244.29   <pending>     80:31867\/TCP   20s\ntuxninja@tldev1:~$<\/pre>\n
Note the EXTERNAL-IP is in a pending state, once the LoadBalancer is created, this will have an IP address.<\/strong><\/p>\n
tuxninja@tldev1:~$ kubectl get svc nginx-deployment\nNAME               TYPE           CLUSTER-IP     EXTERNAL-IP      PORT(S)        AGE\nnginx-deployment   LoadBalancer   10.19.244.29   35.203.155.123   80:31867\/TCP   1m\ntuxninja@tldev1:~$ curl http:\/\/35.203.155.123\n<!DOCTYPE html>\n<html>\n<head>\n<title>Welcome to nginx!<\/title>\n<\/pre>\n
And were all done, congratulations! \ud83d\ude42<\/strong><\/p>\n
In Closing…<\/h3>\n
Kubernetes is cool as a fan<\/strong>, and setting it up on GCP is almost as easy as pressing the big EASY button<\/a>.<\/strong> We have barely scraped the surface here so for continued learning I recommend buying Kubernetes Up & Running<\/a> by Kelsey Hightower<\/a>, Brendan Burns<\/a><\/strong> and Joe Beda<\/a><\/strong>. I would follow these folks on twitter<\/strong>, and in addition follow Kubernetes Co-Founder Tim Hockin<\/a><\/strong> as well as former Docker, Google, and now Microsoft employee\/guru of all things containers Jessie Frazelle.<\/a><\/strong><\/p>\n
After you are done following these inspirational leaders in the community go to youtube and watch every Kelsey Hightower video you can find<\/strong>. Kelsey Hightower is perhaps the tech communities best presenter and no one has done more to educate and bring Kubernetes to the mainstream than Kelsey. So a quick shout out and thank you to Kelsey for his contributions to the community<\/strong>. In his honor here are two of my favorite videos from Kelsey. [ one<\/a> ] [ two<\/a> ].<\/p>\n","protected":false},"excerpt":{"rendered":"
These days the pace of innovation in DevOps can leave you feeling like you’re jogging on a treadmill programmed to run faster than Usain Bolt. Mastery requires hours of practice and the last decade in DevOps has not allowed for it. Before gaining 10 years of experience running virtual machines using VmWare in private data-centers, […]<\/p>\n<\/a>","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[130,184,183,1,185],"tags":[132,188,158,186,149,187,189],"class_list":{"0":"post-639","1":"post","2":"type-post","3":"status-publish","4":"format-standard","6":"category-cloud","7":"category-containers","8":"category-gcp","9":"category-howtos","10":"category-kubernetes","11":"tag-cloud","12":"tag-containers","13":"tag-docker","14":"tag-gcp","15":"tag-google-cloud-platform","16":"tag-kubernetes","17":"tag-nginx","18":"h-entry","19":"hentry"},"_links":{"self":[{"href":"https:\/\/tuxlabs.com\/index.php?rest_route=\/wp\/v2\/posts\/639","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/tuxlabs.com\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/tuxlabs.com\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/tuxlabs.com\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/tuxlabs.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=639"}],"version-history":[{"count":32,"href":"https:\/\/tuxlabs.com\/index.php?rest_route=\/wp\/v2\/posts\/639\/revisions"}],"predecessor-version":[{"id":710,"href":"https:\/\/tuxlabs.com\/index.php?rest_route=\/wp\/v2\/posts\/639\/revisions\/710"}],"wp:attachment":[{"href":"https:\/\/tuxlabs.com\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=639"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/tuxlabs.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=639"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/tuxlabs.com\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=639"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}