James Spurin’s Post

𝐈𝐦𝐚𝐠𝐞 𝐏𝐮𝐥𝐥 𝐏𝐨𝐥𝐢𝐜𝐲 In kubernetes when you first create a Deployment, StatefulSet, Pod or any other objects that includes a Pod template, then by default the image pull policy of all the containers in that pod is set to 𝐈𝐟𝐍𝐨𝐭𝐏𝐫𝐞𝐬𝐞𝐧𝐭, if any other is not explicitly specified. This image pull policy specifications lets you specify how you want the kubelet to pull an image and for that we have three main policies namely: 🔷𝐈𝐟𝐍𝐨𝐭𝐏𝐫𝐞𝐬𝐞𝐧𝐭: This is the default policy, with the imagePullPolicy set to IfNotPresent it will pull the image only if it is not already present on the node. 🔷𝐀𝐥𝐰𝐚𝐲𝐬: If the imagePullPolicy is set to Always, then it pulls the image from the registry, regardless of whether it is already present on the node. 🔷𝐍𝐞𝐯𝐞𝐫: If the imagePullPolicy is set to Never, then it will never pull the image from the registry and only uses the image if it is already present on the node. 𝐃𝐞𝐟𝐚𝐮𝐥𝐭 𝐈𝐦𝐚𝐠𝐞 𝐏𝐮𝐥𝐥 𝐏𝐨𝐥𝐢𝐜𝐲 Sometimes the imagePullPolicy is not specified. In such cases the 𝐝𝐞𝐟𝐚𝐮𝐥𝐭 image pull policy is set when specific conditions are met: 🔷If you do not specify imagePullPolicy field and just give the container image, the policy is automatically set to IfNotPresent. 🔷If you do not specify imagePullPolicy field and the tag given is latest, then the policy is automatically set to Always. 🔷If you do not specify imagePullPolicy field as well as the tag for the image, then the policy is automatically set to Always. 🔷If you do not specify imagePullPolicy field and specify any tag other than the latest, then the policy is automatically set to IfNotPresent. If you found this post useful, give it a like👍 Repost♻️ Follow Bala Vignesh Manoharan for more such posts 💯🚀 #kubernetes #k8s #imagePullPolicy

I'm embarking on a journey to learn Docker! Over the next few weeks, I'll be sharing what I learn about containers, images, and orchestration. If you're also curious about Docker or have tips, let's connect and learn together 😊 ! Docker Container Image is lightweight, standalone executable package of software that includes everything needed to run as application ->code , runtime, system tools, system libraries and settings. Containers vs Virtual Machines 1. Resource Utilisation Containers share the host OS kernel making them lighter and faster than VM's. VM's have a full fledged OS and hypervisor making them more resource intensive. 2. Portability Containers are designed to be portable and can run on any system with compatible host OS. VM's are less portable as they need a compatible hypervisor to run. 3. Security VM's provide a higher level of security as each VM has its own OS and can be isolated from host and other VM's. Containers provide less isolation as they share the OS. 4. Management Managing containers are typically easier than managing VM's as containers are designed to be light weight and fast moving. Containers are light weight because they use containerisation which allows them to share OS's kernel and libraries while still providing isolation for the application and its dependencies. Happy learning 😊 #Docker #SiteReliabilityEngineering #PerformanceEngineering #Devops Thank You 😊 Abhishek Veeramalla Vikas Yadav Sandip Das Savinder Puri Shubham Londhe

We’re taking the exciting enhancements of the #kubernetes v1.30 release and breaking them down into the simplest terms possible. Think of it as Kubernetes explained by your non-techie friend who’s really good at making complex stuff sound like a piece of cake. Whether you’re a seasoned developer, an IT professional, or just a curious observer of the tech world, our aim is to provide you with an understanding of what’s new and why it matters, minus the headache of #decoding technical speak. #learnwitharun Check out this article 👇 https://lnkd.in/gcsbxTD8

🚀 𝐃𝐚𝐲 𝟏𝟒/𝟒𝟎 𝐨𝐟 #𝟒𝟎𝐝𝐚𝐲𝐬𝐨𝐟𝐤𝐮𝐛𝐞𝐫𝐧𝐞𝐭𝐞𝐬: 𝐊𝐮𝐛𝐞𝐫𝐧𝐞𝐭𝐞𝐬 𝐓𝐚𝐢𝐧𝐭𝐬 𝐚𝐧𝐝 𝐓𝐨𝐥𝐞𝐫𝐚𝐭𝐢𝐨𝐧𝐬 !! ❓🤔 Why use Taints and Tolerations when we can manually schedule pods using nodeName? ❓🤔 Why use NodeSelector and labels when we have Taints and Tolerations? ❓🤔 Which method is used in real-time? Let's understand the concept of Taints and Tolerations as part of our CKA series: 🔹 𝐓𝐚𝐢𝐧𝐭 🚧🚫: Setting up Fences 🔹 𝐓𝐨𝐥𝐞𝐫𝐚𝐭𝐢𝐨𝐧 🎫: Permission slips for Pods to bypass taints. 𝐓𝐚𝐤𝐞𝐚𝐰𝐚𝐲𝐬: 1️⃣ Taints vs Tolerations 2️⃣ Types of Scheduling Tolerations 3️⃣ Practical Examples 4️⃣ NodeSelector and Labels 5️⃣ Taints &Tolerations vs NodeSelector 6️⃣ Limitations of NodeSelector and Next Steps.. Please check out my blog for a detailed breakdown and simplified explanation here 👇 Piyush sachdeva The CloudOps Community #CKASeries #Kubernetes #TaintsAndTolerations #DevOps #CloudComputing #K8s #LearningJourney

You know what a pod is but what does its lifecycle consist of? Let’s find out! 🟨 Stage 1: Pending In this stage, Kubernetes identifies a node that can run the pod's containers, but the container images haven't been taken out of the node. 🟨 Stage 2: Running Once the conditions are favourable and resources are available, the containers execute and perform their designated tasks. 🟨 Stage 3: Success Once all the containers with the pods have fulfilled their tasks, the pods enter the “succeeded” stage. Now let’s assume a scenario where the pod fails to complete the task. 🟨 Stage: Failed The failed pods restart automatically for recovery from failure. 🟨 Stage: Unknown In this stage, Kubernetes fails to determine the pod's status accurately. 🟨 Stage: Terminating Scheduled pods for deletion enter the “Terminating” stage”, where Kubernetes begins shutting down the pod's containers. 🟨 Stage: Terminated Once the termination process is completed, the pod is removed from the cluster. Like / repost if you learned something new! #kubernetes #kubernetescluster #kubernetessecurity #kubernetesmanagement #jumisaTech

I’m happy to share that I’ve obtained a new certification: Docker- SWARM | SERVICES | STACKS - Hands-on Course from KodeKloud!

How Kubernetes picks which pods to delete during scale-in #WorkSmartWithK8s #kubernetes #pods #scaling-in #replicaset #poddeletioncost https://lnkd.in/eAbxuqcV

Check out the cutest Kubernetes release blog by KodeKloud! 🐧✨ Here are the enhancements: 🖥️ Container Resource based Pod Autoscaling (Stable) 🛠️ Introduction of Structured Parameters for Dynamic Resource Allocation (Alpha) 🧠 Node Memory Swap Support (Beta) 🔐 Structured Authentication Configuration (Beta) 👤 User Namespaces in Pods (Beta) 🚀 Speed Up Recursive SELinux Label Change (Beta) ✅ Job Success/Completion Policy (Alpha) 🎮 Interactive Flag Added to kubectl Delete Command (Stable) 🔄 Routing Preferences for Services (Alpha) Join the Kubernetes fun! 🎉 #Kubernetes #Release #1.30 #Uwubernetes https://lnkd.in/gx6fFbA5

What is a ReplicaSet in Kubernetes? A ReplicaSet in Kubernetes is a controller that ensures a specified number of identical Pods are running at all times in a cluster. The main purpose of a ReplicaSet is to maintain the desired number of Pods in a running state, ensuring high availability and reliability of your application. #devops #tools #kubernetes #replicaset #tutorial #practical #kubernete #devopstools #pods #cluster #tools #devops #Kubernetes

From Local Containers to Kubernetes Using Podman to generate Kubernetes manifests Very interesting post about how to use Podman to generate Kubernetes manifests. It is incredible how Podman is evolving. I wish they will keep the current licensing and not moving to a more restrictive one like Docker in the future. https://lnkd.in/dziZ5aGe #containers #kubernetes #podman #coolstuff