Automatic Restarting of Pods inside Replication Controller of Kubernetes Cluster


A key feature of Kubernetes is its ability to maintain the “desired state” using declared primitives. Replication Controllers is a key concept that helps achieve this state.

A replication controller ensures that a specified number of pod “replicas” are running at any one time. If there are too many, it will kill some. If there are too few, it will start more.

Replication Controller

Lets take a look on how to spin up a Replication Controller with two replicas of a Pod. Then we’ll kill one pod and see how Kubernetes will start another Pod automatically.

Start Kubernetes Cluster

  1. Easiest way to start a Kubernetes cluster on a Mac OS is using Vagrant:
  2. Alternatively, Kubernetes can be downloaded from, and cluster can be started as:

Start and Verify Replication Controller and Pods

  1. All configuration files required by Kubernetes to start Replication Controller are in kubernetes-java-sample project.  Clone the workspace:
  2. Start a Replication Controller that has two replicas of a pod, each with a WildFly container:
    The configuration file used is shown:
    Default WildFly Docker image is used here.
  3. Get status of the Pods:
    Notice -w refreshes the status whenever there is a change. The status changes from Pending to Running and then Ready to receive requests.
  4. Get status of the Replication Controller:
    If multiple Replication Controllers are running then you can query for this specific one using the label:
  5. Get name of the running Pods:
  6. Find IP address of each Pod (using the name):
    And of the other Pod as well:
  7. Pod’s IP address is accessible only inside the cluster. Login to the minion to access WildFly’s main page hosted by the containers:

Automatic Restart of Pods

Lets delete a Pod and see how a new Pod is automatically created.

Notice how the Pod with name wildfly-rc-15xg5 was deleted and a new Pod with the name wildfly-rc-0xoms was created.

Finally, delete the Replication Controller:

The latest configuration files and detailed instructions are at kubernetes-java-sample.

In real world, you’ll typically wrap this Replication Controller in a Service and front-end with a Load Balancer. But that’s a topic for another blog!


Be Sociable, Share!
  • Tweet

9 thoughts on “Automatic Restarting of Pods inside Replication Controller of Kubernetes Cluster

  1. Pingback: Automatic Restarting of Pods inside Replication Controller of Kubernetes Cluster | Social Marketing by WordPress
  2. Pingback: Scaling Kubernetes Cluster | Social Marketing by WordPress
  3. Pingback: This week in JBoss (18th July 2015): Containers, clusters and more | Social Marketing by WordPress
  4. Hello buddy, you are a true rockstar.
    Rana ki putli phiri nahin,
    Tab tak Chetak mud jata tha.

  5. If you are here to know about bing rewards so you can find out here one of the best portal bing rewards bot which will provide you all exact information by which your work will be all easier.

  6. Think about every one of the unproductive processes I am going to trigger when I eventually affect the bank. Your trainers can then concentrate on their business best – developing skills.

  7. I like your all post. You have done really good work. Thank you for the information you provide, it helped me a lot. I hope to have many more entries or so from you.

Leave a Reply

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