• AKS 26 – why Ingress

    Why Use Ingress Over LoadBalancer? For any ecommerce website there will be more then 200 services Problems with LoadBalancer services: Client Request↓[Ingress Controller] ← Watches Ingress Resources↓[Load Balancer] ← Configured by Controller↓[Services] → [Pods]…

    Continue reading…

  • AKS 25 -Kubernetes services

    Service Types Overview 1. ClusterIP (Default) Characteristics: apiVersion: v1kind: Servicemetadata:name: payments-servicespec:type: ClusterIPselector:app: paymentsports:– port: 80targetPort: 8080 2. NodePort Characteristics: apiVersion: v1kind: Servicemetadata:name: payments-servicespec:type: NodePortselector:app: paymentsports:– port: 80targetPort: 8080nodePort: 32000 # Optional, auto-assigned if not…

    Continue reading…

  • AKS 25 – Readiness and Liveness Probes

    Readiness Probes – In Detail Purpose and Function Readiness probes determine if a container is ready to accept traffic. When a pod is not ready: Liveness Probes – In Detail Purpose and Function Liveness…

    Continue reading…

  • AKS 24 – Practical Of AKS and all component

    Set Up Azure CLI and Create AKS Cluster Install Azure CLI (if not already installed) On Ubuntu/Debian: curl -sL https://aka.ms/InstallAzureCLIDeb | sudo bash Login to Azure az login Create a resource group az group…

    Continue reading…

  • AKS Q&A 3

     What is the most basic deployment unit in Kubernetes? A: In Kubernetes, the most basic unit of deployment is a Pod. While Docker deals directly with containers, Kubernetes introduces the concept of Pods as a wrapper…

    Continue reading…

  • AKS 23 – Network Policies in AKS

    Network Policies in Kubernetes control how pods communicate with each other and with external endpoints. They define rules for ingress (incoming) and egress (outgoing) traffic. Why Use Network Policies? Benefit Description Security Prevent unauthorized…

    Continue reading…