<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>production on Dileep Kumar</title>
    <link>https://dileepkumar.dev/tags/production/</link>
    <description>Recent content in production on Dileep Kumar</description>
    <image>
      <title>Dileep Kumar</title>
      <url>https://dileepkumar.dev/papermod-cover.png</url>
      <link>https://dileepkumar.dev/papermod-cover.png</link>
    </image>
    <generator>Hugo -- gohugo.io</generator>
    <language>en</language>
    <lastBuildDate>Mon, 13 Jan 2025 00:35:00 +0530</lastBuildDate><atom:link href="https://dileepkumar.dev/tags/production/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Kubernetes Health Probes: Liveness, Readiness, and Startup Probes Explained</title>
      <link>https://dileepkumar.dev/post/kubernetes-health-probes/</link>
      <pubDate>Mon, 13 Jan 2025 00:35:00 +0530</pubDate>
      
      <guid>https://dileepkumar.dev/post/kubernetes-health-probes/</guid>
      <description>Introduction Kubernetes needs to know when your applications are healthy and ready to serve traffic. Health Probes enable Kubernetes to automatically detect and recover from application failures, ensuring high availability.
Understanding Health Probes The Problem Without Probes:
Crashed applications continue receiving traffic Deadlocked processes never recover Slow-starting apps receive traffic too early Failed containers remain in &amp;ldquo;Running&amp;rdquo; state The Solution: Health probes provide automated health monitoring and recovery:
Automatic restart of failed containers Traffic routing only to healthy pods Graceful startup for slow applications Self-healing without manual intervention Types of Probes - Complete Comparison Probe Type Purpose Action on Failure When to Use Liveness Is container alive?</description>
    </item>
    
    <item>
      <title>Production Kubernetes Cluster Setup with Kubeadm and Containerd</title>
      <link>https://dileepkumar.dev/post/kubernetes-production-cluster-setup/</link>
      <pubDate>Mon, 13 Jan 2025 00:30:00 +0530</pubDate>
      
      <guid>https://dileepkumar.dev/post/kubernetes-production-cluster-setup/</guid>
      <description>Introduction Setting up a production-ready Kubernetes cluster requires careful planning and configuration. This guide walks you through creating a multi-node cluster using kubeadm and containerd as the container runtime.
Prerequisites Minimum Requirements:
2 GB RAM per machine 2 CPUs per machine Network connectivity between machines Unique hostname, MAC address, product_uuid Swap disabled Recommended for Production:
3+ control plane nodes (HA) 3+ worker nodes 4 GB+ RAM per node Load balancer for control plane Architecture Load Balancer (Optional for HA) ↓ Control Plane Nodes (3) ↓ Worker Nodes (3+) Step 1: Prepare All Nodes On all nodes (control plane + workers):</description>
    </item>
    
    <item>
      <title>Kubernetes Monitoring with Prometheus and Grafana: Complete Setup Guide</title>
      <link>https://dileepkumar.dev/post/kubernetes-monitoring-prometheus-grafana/</link>
      <pubDate>Mon, 13 Jan 2025 00:25:00 +0530</pubDate>
      
      <guid>https://dileepkumar.dev/post/kubernetes-monitoring-prometheus-grafana/</guid>
      <description>Introduction Production Kubernetes clusters require robust monitoring. Prometheus collects metrics, while Grafana visualizes them, providing complete observability into your cluster&amp;rsquo;s health and performance.
Architecture Kubernetes Cluster ↓ Prometheus (Metrics Collection) ↓ Grafana (Visualization) ↓ Dashboards &amp;amp; Alerts Installing with Helm Add Prometheus Community Helm repo:
helm repo add prometheus-community https://prometheus-community.github.io/helm-charts helm repo update Install kube-prometheus-stack:
helm install prometheus prometheus-community/kube-prometheus-stack \ --namespace monitoring \ --create-namespace Verify installation:
kubectl get pods -n monitoring kubectl get svc -n monitoring Accessing Grafana Port forward:</description>
    </item>
    
    <item>
      <title>Kubernetes Ingress: Advanced HTTP Routing and Load Balancing</title>
      <link>https://dileepkumar.dev/post/kubernetes-ingress-guide/</link>
      <pubDate>Mon, 13 Jan 2025 00:15:00 +0530</pubDate>
      
      <guid>https://dileepkumar.dev/post/kubernetes-ingress-guide/</guid>
      <description>Introduction Exposing multiple services with LoadBalancer creates multiple cloud load balancers (expensive!). Ingress provides HTTP/HTTPS routing to multiple services using a single load balancer, with features like path-based routing, SSL termination, and virtual hosting.
Understanding Kubernetes Ingress The Problem Without Ingress:
Service 1 → LoadBalancer ($$$) Service 2 → LoadBalancer ($$$) Service 3 → LoadBalancer ($$$) Total: 3 load balancers, high cost! The Solution With Ingress:
┌─→ Service 1 Ingress Controller ─┼─→ Service 2 (Single LB) └─→ Service 3 Total: 1 load balancer, low cost!</description>
    </item>
    
    <item>
      <title>Kubernetes Advanced Scheduling: Node Affinity, Taints, and Tolerations</title>
      <link>https://dileepkumar.dev/post/kubernetes-advanced-scheduling/</link>
      <pubDate>Mon, 13 Jan 2025 00:05:00 +0530</pubDate>
      
      <guid>https://dileepkumar.dev/post/kubernetes-advanced-scheduling/</guid>
      <description>Introduction By default, Kubernetes scheduler automatically places Pods on available nodes. But what if you need more control? Perhaps you want GPU-intensive workloads on specific nodes, or need to isolate production from development workloads. Node Affinity, Taints, and Tolerations give you fine-grained control over Pod placement.
Understanding Kubernetes Scheduling Default Scheduler Behavior: The Kubernetes scheduler automatically assigns Pods to nodes based on:
Available resources (CPU, memory) Node conditions (ready, disk pressure, memory pressure) Pod resource requests and limits Quality of Service (QoS) class Why Advanced Scheduling?</description>
    </item>
    
    <item>
      <title>Kubernetes Configuration Management: Mastering ConfigMaps and Secrets</title>
      <link>https://dileepkumar.dev/post/kubernetes-configuration-management/</link>
      <pubDate>Sun, 12 Jan 2025 23:45:00 +0530</pubDate>
      
      <guid>https://dileepkumar.dev/post/kubernetes-configuration-management/</guid>
      <description>Introduction Hardcoding configuration values and sensitive data directly into your application code is a recipe for disaster. It makes your applications inflexible, insecure, and difficult to manage across different environments. Kubernetes provides two powerful objects to solve this problem: ConfigMaps for configuration data and Secrets for sensitive information.
In this comprehensive guide, I&amp;rsquo;ll show you how to effectively manage application configuration and secrets in Kubernetes, following security best practices and production patterns.</description>
    </item>
    
    <item>
      <title>Kubernetes Services Deep Dive: ClusterIP, NodePort, and LoadBalancer Explained</title>
      <link>https://dileepkumar.dev/post/kubernetes-services-deep-dive/</link>
      <pubDate>Sun, 12 Jan 2025 23:40:00 +0530</pubDate>
      
      <guid>https://dileepkumar.dev/post/kubernetes-services-deep-dive/</guid>
      <description>Introduction In Kubernetes, Pods are ephemeral - they can be created, destroyed, and replaced at any time. This creates a challenge: how do you reliably connect to your applications when Pod IP addresses constantly change? The answer is Kubernetes Services.
Services provide stable networking endpoints for your Pods, enabling reliable communication both within your cluster and from external clients. In this comprehensive guide, I&amp;rsquo;ll walk you through the three main Service types - ClusterIP, NodePort, and LoadBalancer - with practical examples and production best practices.</description>
    </item>
    
    <item>
      <title>Mastering Kubernetes Deployments: Scaling, Rolling Updates, and Rollbacks</title>
      <link>https://dileepkumar.dev/post/kubernetes-deployments-mastery/</link>
      <pubDate>Sun, 12 Jan 2025 23:35:00 +0530</pubDate>
      
      <guid>https://dileepkumar.dev/post/kubernetes-deployments-mastery/</guid>
      <description>Introduction While Pods are the fundamental units in Kubernetes, you&amp;rsquo;ll rarely create them directly in production. Instead, you&amp;rsquo;ll use Deployments - a higher-level abstraction that provides declarative updates, scaling, and self-healing capabilities for your applications.
In this comprehensive guide, I&amp;rsquo;ll walk you through everything you need to know about Kubernetes Deployments, from basic creation to advanced rollout strategies and rollback procedures. This is essential knowledge for anyone managing production Kubernetes workloads.</description>
    </item>
    
  </channel>
</rss>
