Vishnu_VVV

Kubernetes probes are health checks that the kubelet (the node agent) performs on containers running inside a Pod. Their primary purpose is to let Kubernetes know the state of your application so it can make intelligent decisions, like restarting a failing container or not sending traffic to a pod that isn't ready. There are three distinct types of probes, each serving a different purpose: Liveness Probe (livenessProbe)  Purpose : Answers the question, "Is the application alive and running?"  Action : If a liveness probe fails, the kubelet restarts the container. Use Case : To recover from a "deadlock" or a situation where the application is running but is unable to make any progress. A classic example is a web server that has stopped responding to HTTP requests. Readiness Probe (readinessProbe)         Purpose : Answers the question, "Is the application ready to accept traffic?"          Action : If a readiness probe fails, th...

Benifits of Autoscaling: High/Improved availability of the application Elasticity Bettter resource utilization Seamless load management   There are 2 types of Auto scaling  Vertical scaling :  Increasing the capacity of the same single system Horizontal scaling : Increasing number of instances/servers/pods  In the world of devops, horizontal scaling is best  HPA : Horizontal POD Autoscaling --> Used to scale up/down no of POD replicas based on observed metris (CPU or memory utilization) It observes all the required metrics, based on that it will add the PODS Tracks multiple metrics, accordingly it will adjust the PODS HPA will interact with Metric server to identify CPU/Memory utilization  VPA : Vertical POD Autoscaling Metric server  is an application that collects metrics from PODS, nodes according to state of CPU and Memory.  Metric server will not be present by default in the K8S Cluster The Metrics Server is a scalable, efficient sour...