How to Deploy a Pod in a Replication Controller on Kubernetes

Описание: Learn the steps to deploy a pod and manage scaling effectively in Kubernetes through a replication controller alternative, with practical commands and explanations in simple language.
---
This video is based on the question https://stackoverflow.com/q/65398545/ asked by the user 'Chris F' ( https://stackoverflow.com/u/1401560/ ) and on the answer https://stackoverflow.com/a/65398756/ provided by the user 'Chris F' ( https://stackoverflow.com/u/1401560/ ) at 'Stack Overflow' website. Thanks to these great users and Stackexchange community for their contributions.

Visit these links for original content and any more details, such as alternate solutions, latest updates/developments on topic, comments, revision history etc. For example, the original title of the Question was: In k8s, how to deploy a pod in a replication controller?

Also, Content (except music) licensed under CC BY-SA https://meta.stackexchange.com/help/l...
The original Question post is licensed under the 'CC BY-SA 4.0' ( https://creativecommons.org/licenses/... ) license, and the original Answer post is licensed under the 'CC BY-SA 4.0' ( https://creativecommons.org/licenses/... ) license.

If anything seems off to you, please feel free to write me at vlogize [AT] gmail [DOT] com.
---
Introduction

Kubernetes (often referred to as K8s) can be quite overwhelming for newcomers, especially when dealing with deployments and replication. A common concern for beginners is understanding how to effectively create and manage pods using replication controllers. If you've found yourself in a situation where your attempts to follow the outdated examples in "Kubernetes in Action" have left you confused, you’re not alone. In this post, we'll explore how to successfully deploy a pod in a replication controller or, more effectively, how to utilize deployments which are the standard approach in modern Kubernetes.

Understanding the Problem

When you first execute commands to create a pod that should be managed by a replication controller (RC), you may notice that the RC is not created as expected. For instance, if you’ve run the command:

[[See Video to Reveal this Text or Code Snippet]]

You might see the output indicating that the pod was created, but when querying for RCs using:

[[See Video to Reveal this Text or Code Snippet]]

You find no resources listed. This discrepancy occurs because the Kubernetes command syntax and functionality have evolved, and the --generator flag is now deprecated.

The Solution: Using Deployments Instead of Replication Controllers

Why Use Deployments?

Instead of replication controllers, Kubernetes now encourages the use of deployments. Deployments provide a more powerful and qualified approach for managing pods, including scaling and updating them over time. Here’s how you can create a deployment and manage your pod accordingly.

Step-by-Step Guide to Creating a Deployment

Create the Deployment:
You can create a deployment using the kubectl create deploy command. Here’s how to create a deployment for the kubia pod:

[[See Video to Reveal this Text or Code Snippet]]

After this command is run, you'll receive a confirmation like:

[[See Video to Reveal this Text or Code Snippet]]

Check the Deployment Status:
To verify that the deployment was created, you can run:

[[See Video to Reveal this Text or Code Snippet]]

You should see a status report including the number of pods that are ready, up-to-date, and available.

Scale the Deployment:
To scale your deployment to 3 replicas, use the following command:

[[See Video to Reveal this Text or Code Snippet]]

This command will scale your deployment, and upon checking the pods, you should see three instances running:

[[See Video to Reveal this Text or Code Snippet]]

Expose the Deployment:
Finally, to make your pod accessible, you can expose the deployment as a service:

[[See Video to Reveal this Text or Code Snippet]]

This command creates a service that can be accessed via a LoadBalancer.

Confirming Your Setup

After following these steps, you should have a fully functional deployment with three replicas of your pod running. You can access the deployed application via the exposed LoadBalancer.

Conclusion

Transitioning from a traditional replication controller approach to using deployments in Kubernetes helps streamline the pod management process. As Kubernetes evolves, using deployments not only simplifies scaling and updating but also aligns best with current best practices. Whether you are a beginner or an experienced user, understanding these changes is essential for effectively managing Kubernetes workloads.

For those just starting, don’t hesitate to explore the latest documentation and guides, as staying updated is key in the cloud-native ecosystem.