Webinar Series: Getting Started with Kubernetes

This informative article supplements a series that is webinar deploying and managing containerized workloads in the cloud. The series covers the essentials of containers, including container that is managing, deploying multi-container applications, scaling workloads, and working together with Kubernetes. It highlights recommendations for operating applications that are stateful

This guide includes the principles and commands in 3rd session for the show, getting to grips with Kubernetes.


In the tutorial that is previous this series, we explored managing multi-container applications with Docker Compose. While the Docker Command Line Interface (CLI) and Docker Compose can deploy and scale containers running on a machine that is single Kubernetes is made to manage multi-container applications implemented across numerous devices or hosts.

Kubernetes is an container that is open-source tool for managing containerized applications. A Kubernetes cluster has two components that are key Master Nodes and Worker Nodes. Some Master Nodes become the control airplane that manage the employee Nodes and implemented applications. The employee Nodes would be the workhorses of a Kubernetes group which are accountable for operating the applications that are containerized

The Master Nodes expose an API by which the command-line tools and clients that are rich a job, which contains the definition of an application. Each application consists of one or more containers, the storage definitions and the internal and ports that are external that they are exposed. The control airplane operating on Master Nodes schedules the containers in just one of the employee Nodes. Whenever a credit card applicatoin is scaled, the control airplane launches extra containers on some of the available employee Nodes.

For a introduction that is detailed Kubernetes, make reference to the tutorial An Introduction to Kubernetes.

StackPointCloud deploys a Kubernetes group in three actions making use of a interface that is web-based. It hides the complexity of installing and configuring Kubernetes through a user experience that is simplified. DigitalOcean is certainly one of StackPoint’s supported cloud platforms. Designers that unfamiliar with systems configuration and administration may use StackPoint to put in Kubernetes on DigitalOcean quickly. For precisely the supported features and prices, make reference to their website.

In this guide, you are going to create and configure Kubernetes on DigitalOcean through StackPoint and deploy a application that is containerized your group.


To follow this guide, you will require

  • A neighborhood device utilizing the curl demand set up, that you can used to down load a command-line device to handle your Kubernetes group. The curl demand is set up on macOS and Ubuntu 16.04.
  • A DigitalOcean account. Within guide, you are going to utilize StackPoint to get in touch towards DigitalOcean provision and account three 1GB Droplets.

Step 1 – Installing Kubernetes

To begin installing Kubernetes on DigitalOcean, check out Stackpoint.io and then click in the Login key.

The StackPoint web page

This goes to a typical page where you could select an identification provider and join with current qualifications. Select DigitalOcean from list and join along with your DigitalOcean password and username.

Choosing a Provider

On the page that is next select DigitalOcean from variety of available cloud platforms.

Select the DigitalOcean provider

You are now able to configure the group. Click the EDIT key to modify the settings the DigitalOcean provider:

DigitalOcean provider overview

This goes towards Configure company display screen.

DigitalOcean provider configuration page

Choose an area of the option from Region dropdown list. You are able to keep one other settings at their standard values. Click Submit while done.

On the screen that is next enter a group title of the option and then click Submit.

Enter the cluster name

The group installation will now begin and you’ll be studied to a typical page where you could monitor the cluster’s progress. The installation shall just take about 15 mins.

The status of your cluster

Once the group is configured, we could set a command-line tool up to assist it.

Step 2 – Configuring the Kubernetes CLI

To speak to the Kubernetes group operating in DigitalOcean, we truly need a demand line device inside our development device. We are going to utilize kubectl, the CLI for Kubernetes.

Run these commands to put in kubectl from Bing’s servers:

  • curl -LO https://storage.googleapis.com/kubernetes-release/release/`curl -s https://storage.googleapis.com/kubernetes-release/release/stable.txt`/bin/darwin/amd64/kubectl

You’ll see this production:


percent Complete percent Gotten percent Xferd Average Speed Time Time Time Active Dload Upload Complete Devoted Left Speed 100 63.7M 100 63.7M 0 0 5441k 0 0:00:12 0:00:12 --:--:-- 4644k

The kubectl binary had been installed towards present directory, Let’s replace the permissions for the installed binary and go it towards /usr/local/bin directory from anywhere:( so we can run it****)

  • chmod +x ./kubectl
  • sudo mv ./kubectl /usr/local/bin/kubectl

Now let’s point the kubectl software at our Kubernetes group. For that, we must install a configuration file from Stackpoint. Go back to the group status web page inside web browser. After confirming your group is prepared and stable, click the group title as shown in figure that is following****)

The cluster name

Click in the kubeconfig website link in menu that is left-hand down load the setup file towards neighborhood device:


Back inside terminal, set the surroundings adjustable KUBECONFIG towards course for the file that is downloaded. Presuming your file downloaded towards Downloads folder in your house directory, you would issue this demand:

  • export KUBECONFIG=~/Downloads/kubeconfig

With kubectl configured, let’s verify we could talk to our group.

Step 3 – confirming the Kubernetes Installation

Now that individuals have actually the completely configured group combined with customer, let’s operate a commands that are few validate the surroundings.

Run the command that is following get information regarding the group.

You’ll see this production:


Kubernetes master is operating at Heapster is operating at KubeDNS is operating at To debug that is further diagnose group issues, utilize 'kubectl cluster-info dump'.

The production confirms your group is working which the Kubernetes Master Nodes are ready to go.

Next, let’s verify the healthiness of all elements operating in Master Nodes. In the event that group is simply configured, it might take sometime before all elements reveal a status that is healthy. These components are a right part for the Kubernetes Master Nodes that become the control airplane.

Execute this demand:

You’ll see this production:


NAME REPUTATION MESSAGE MISTAKE Scheduler ok that is healthy Controller-manager ok that is healthy etcd-0 healthier {"health": "true"}

Finally, let’s list all nodes for the operating Kubernetes group.

You’ll see production similar to this:


NAME REPUTATION ROLES AGE VARIATION spc52y2mk3-master-1 prepared master 29m v1.8.5 spc52y2mk3-worker-1 prepared <none> 22m v1.8.5 spc52y2mk3-worker-2 prepared <none> 22m v1.8.5

This verifies your group with one Master Node and two employee Nodes is prepared for all of us to deploy applications. Therefore let us deploy a credit card applicatoin towards group.

Step 4 – Deploying and Accessing a credit card applicatoin

Let’s launch a Nginx that is simple web and access its standard website from our neighborhood device. Execute this demand to pull the Nginx image from Docker Hub and produce a deployment called myweb:

  • kubectl run --image=nginx:latest myweb

This demand is comparable to the docker run demand, except so it packages and deploys the container in a artifact that is kubernetes-specific a Pod. You’ll learn more about Pods in the part that is next of show.

once you perform the demand, you’ll see this production:


deployment "myweb" produced

Now make sure that the Pod is done utilizing the nginx container:

You’ll see this production:


NAME SET REPUTATION RESTARTS AGE myweb-59d7488cb9-jvnwn 1/1 operating 0 3m

To access the internet host operating in the Pod, we must expose it towards general public Web. We make that happen utilizing the command that is following****)

  • kubectl expose pod**********************************************************************)d that is myweb-(************************************************)cb9-jvnwn --port=80 --target-port=80 --type=NodePort


service "myweb-59d7488cb9-jvnwn" exposed

The Pod happens to be exposed on every Node for the group on an port that is arbitrary. The --port and --target-port switches indicate the ports through which the web server becomes available. The switch --NodePortensures that any node can be used by us in the group to get into the applying.

To have the NodePort for the myweb implementation, operate the command that is following

  • kubectl get svc**********************************************************************)d that is myweb-(************************************************)cb9-jvnwn


NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE myweb-59d7488cb9-jvnwn NodePort <none> 80:31930/TCP 6m

In this situation, the NodePort is port 31930. This port is used by every Worker Node to react to HTTP demands. Let’s test that away.

Use the DigitalOcean Console for the ip of 1 for the employee Nodes.


Use the curl demand to help make an HTTP demand to at least one for the nodes on slot 31930.

  • curl http://your_worker_1_ip_address:31930/

You’ll understand reaction containing the default that is nginx web page:


<!DOCTYPE html> <html> <head> <title>Welcome to nginx!</title> ... Commercial help can be obtained at <a href="http://nginx.com/">nginx.com</a>.</p> <p><em>Thank you for making use of nginx.</em></p> </body> </html>

You have actually effectively implemented a application that is containerized your Kubernetes group.


Kubernetes is a container management platform that is popular. StackPoint makes it simple to put in Kubernetes on DigitalOcean.

In the part that is next of show, we shall explore the inspiration of Kubernetes much more information.

Reputation for the computer

Previous article

Just how to Install Froxlor control interface

Next article

You may also like


Leave a reply

Your email address will not be published. Required fields are marked *