Gokul Pisharody's Blog

Day-33-devops

Deploying Your First Application in Kubernetes: A Comprehensive Guide

Gokul Pisharody's photo
Gokul Pisharody
·

3 min read

TLDR: This blog post provides a detailed guide on deploying your first application in Kubernetes, covering essential concepts such as Pods, YAML specifications, and the use of kubectl for managing Kubernetes clusters. It emphasizes the importance of understanding the differences between Docker and Kubernetes, and the advantages of using Pods for container orchestration.

Welcome back to the complete DevOps course! In this post, we will explore how to deploy your first application in Kubernetes. If you haven't already, I highly recommend watching the previous videos (Day 30, 31, and 32) to understand the foundational concepts of Docker and Kubernetes, including their architectures and installation processes.

Understanding Kubernetes vs. Docker

Before diving into Kubernetes, it's crucial to understand the differences between Docker and Kubernetes. Here are some key advantages of Kubernetes:

  1. Cluster Management: Kubernetes operates as a cluster, allowing for better resource management.

  2. Auto Scaling: Kubernetes can automatically scale applications based on demand.

  3. Auto Healing: It can automatically replace failed containers.

  4. Enterprise-Level Behavior: Kubernetes supports complex applications and services.

Key Terminologies in Kubernetes

To effectively use Kubernetes, you need to familiarize yourself with some key terminologies:

  • Pod: The smallest deployable unit in Kubernetes, which can contain one or more containers.

  • YAML: A human-readable data serialization format used for configuration files in Kubernetes.

  • kubectl: The command-line tool for interacting with Kubernetes clusters.

What is a Pod?

In Kubernetes, a Pod is a wrapper around one or more containers. Unlike Docker, where you deploy containers directly, Kubernetes requires you to deploy applications as Pods. A Pod defines how to run a container and includes specifications such as:

  • API version

  • Pod name

  • Container specifications (image, ports, etc.)

Why Use Pods?

Using Pods allows for:

  • Shared Networking: Containers within the same Pod can communicate via localhost.

  • Shared Storage: Containers can share files easily.

Creating Your First Pod

To deploy your first application, we will create a Pod using a YAML file. Here’s a simple example of a Pod definition:

apiVersion: v1
kind: Pod
metadata:
  name: nginx-pod
spec:
  containers:
  - name: nginx-container
    image: nginx:1.14.2
    ports:
    - containerPort: 80

Deploying the Pod

  1. Save the above YAML configuration in a file named pod.yaml.

  2. Use the following command to create the Pod:

     kubectl create -f pod.yaml     
 # docker run

  3. To check the status of your Pod, run:

     kubectl get pods
 # docker ps

Interacting with Your Pod

To access your Pod, you can use the following command to log into the Kubernetes cluster:

minikube ssh

Once inside, you can verify that your application is running by executing:

curl localhost:80

Managing Your Kubernetes Cluster with kubectl

The kubectl command-line tool is essential for managing your Kubernetes cluster. Here are some common commands:

  • Get Pods: kubectl get pods

  • Describe Pod: kubectl describe pod <pod-name>

  • View Logs: kubectl logs <pod-name>

  • Delete Pod: kubectl delete pod <pod-name>

Conclusion

In this post, we covered the basics of deploying your first application in Kubernetes using Pods. We discussed the importance of understanding Pods, YAML specifications, and how to use kubectl for managing your Kubernetes environment. As you continue your journey in Kubernetes, remember to practice these concepts and refer to the Kubernetes documentation for further learning.

In the next session, we will explore advanced topics such as Deployments, Auto Scaling, and Auto Healing. Stay tuned and happy learning!

Kubernetesk8s