ZipRecruiter’s Post

I Deployed Ruby on Rails Application on k8s and automated with Tekton pipelines for (CI)continuous integration and ArgoCD for (CD)continuous deployment. #k8s #tekton #argocd #DevOps

If you are learning/working on Kubernetes, You should know this feature added in Kubernetes 1.28 👇 Native Sidecar Containers Here is how it works In Kubernetes version 1.28, native sidecar support was introduced through the use of init containers. This is made possible by a new 𝗿𝗲𝘀𝘁𝗮𝗿𝘁𝗣𝗼𝗹𝗶𝗰𝘆 field, set to "Always." Currently, this is an Alpha feature that you can turn on using feature gates. This feature builds on the idea of a "persistent init container." The init container starts first and uses the restartPolicy to gain sidecar capabilities. It runs for the entire life of the Pod. In simple terms, to turn an init container into a sidecar, just add the attribute "restartPolicy: Always" to its specifications. This is an optional setting. If you don't include the restartPolicy, the container will function as a regular init container. Native sidecar supports livenessProbe, readinessProbe, and startupProbe fields. You can add PostStart and PreStop lifecycle handlers as well. I have covered the practical examples of init containers and native sidecars in a dedicated lesson. 𝗡𝗮𝘁𝗶𝘃𝗲 𝗦𝗶𝗱𝗲𝗰𝗮𝗿 𝗖𝗼𝗻𝘁𝗮𝗶𝗻𝗲𝗿𝘀: https://lnkd.in/ee9epP8n To put your learning to the test, try out the init container quiz added to the lesson. 🔁 Feel free to repost and share this with the community :) ------- I write simple guides on Kubernetes with practical examples to help you learn it, use it better, and prepare for job interviews. All you need is the patience to read through and try out the hands-on tasks. To stay updated on my next Kubernetes post, click the 🔔 on my profile. #kubernetes #devops #devopsengineer

☸ What happens when you make a Pod creation request to Kubernetes? 🤔 Often asked during interviews, this is a classic question designed to test how well you understand the role of each Kubernetes component, its big picture and the flow of requests through these components. So here’s my answer to it 👇 1. I create my Container image and publish it to a repository 2. I use a client like kubectl to send a request to the Kubernetes API to run my application container as a Pod 3. The API checks for my authentication and authorization to make sure I’m allowed to do this stuff. It also makes sure that I’ve sent a valid request with all the necessary information. 4. The API then creates a Pod entry in Etcd storage and sends the Pod’s specification to the scheduler to find a suitable worker node for it. 5. The scheduler analyses the PodSpec and the current state of all available worker nodes and finds the optimal node. 6. It then notifies the API server about the node assigned for the Pod. 7. At this point the Job Controller, which is part of the Controller Manager, discovers from its task list that a Pod has been assigned a Node but the node is not yet running it. Therefore, the system needs to be moved towards the desired state. So the Job controller notifies the API that a Pod needs to be started on the assigned worker node. 8. API notifies The Kubelet on the assigned node, supplying it the PodSpec and all the details. 9. Kubelet talks to the Container runtime on its node to get things going. 10. The Runtime fetches my Image from the repository, starts running the containers and hence, the Pod starts running. 11. Now the Job Controller is happy, the API is notified and of course, all state is saved in etcd. And hence, the request is complete. At this point if I use kubectl to get the status of my Pod, it will show me that my Pod is running. #education #tech #kubernetes #devops #engineering #learning

➡️𝐖𝐡𝐲 𝐝𝐨𝐞𝐬𝐧'𝐭 𝐭𝐡𝐞 𝐊𝐮𝐛𝐞𝐫𝐧𝐞𝐭𝐞𝐬 𝐒𝐜𝐡𝐞𝐝𝐮𝐥𝐞𝐫 𝐬𝐜𝐡𝐞𝐝𝐮𝐥𝐞 𝐚𝐧𝐲 𝐩𝐨𝐝𝐬 𝐨𝐧 𝐭𝐡𝐞 𝐦𝐚𝐬𝐭𝐞𝐫 𝐧𝐨𝐝𝐞? When a Kubernetes cluster is first set up, a taint is automatically applied to the master node with 𝐧𝐨𝐝𝐞-𝐫𝐨𝐥𝐞.𝐤𝐮𝐛𝐞𝐫𝐧𝐞𝐭𝐞𝐬.𝐢𝐨/𝐦𝐚𝐬𝐭𝐞𝐫:𝐍𝐨𝐒𝐜𝐡𝐞𝐝𝐮𝐥𝐞 This taint prevents any pods from being scheduled on the master node by default. ➡️𝐖𝐡𝐚𝐭 𝐚𝐫𝐞 𝐓𝐚𝐢𝐧𝐭𝐬 𝐚𝐧𝐝 𝐓𝐨𝐥𝐞𝐫𝐚𝐭𝐢𝐨𝐧𝐬? - Node affinity is a property of Pods that attracts them to a set of nodes (either as a preference or a hard requirement). Taints are the opposite -- they allow a node to repel a set of pods. - Tolerations are applied to pods. Tolerations allow the scheduler to schedule pods with matching taints. Tolerations allow scheduling but don't guarantee scheduling: the scheduler also evaluates other parameters as part of its function. - 𝐓𝐚𝐢𝐧𝐭𝐬 𝐚𝐧𝐝 𝐭𝐨𝐥𝐞𝐫𝐚𝐭𝐢𝐨𝐧𝐬 𝐰𝐨𝐫𝐤 𝐭𝐨𝐠𝐞𝐭𝐡𝐞𝐫 𝐭𝐨 𝐞𝐧𝐬𝐮𝐫𝐞 𝐭𝐡𝐚𝐭 𝐩𝐨𝐝𝐬 𝐚𝐫𝐞 𝐧𝐨𝐭 𝐬𝐜𝐡𝐞𝐝𝐮𝐥𝐞𝐝 𝐨𝐧𝐭𝐨 𝐢𝐧𝐚𝐩𝐩𝐫𝐨𝐩𝐫𝐢𝐚𝐭𝐞 𝐧𝐨𝐝𝐞𝐬. One or more taints are applied to a node; this marks that the node should not accept any pods that do not tolerate the taints. #Kubernetes #DevOps #CloudComputing #Containers #DevSecOps #DevSecOps #ContinuousIntegration #ContinuousDeployment #Kubernetes #Jenkins #ArgoCD #React #TailwindCSS #WebDevelopment #Developer #FrontendDevelopment #Coding #WebDesign #devops #devopsengineer #devopscommunity #devopsjobs #devopslearning #devopshiring #cloudengineer #ec2 #docker #dockercontainer #kubernetes #job #hiring#ClusterManagement #TechInsights

📣 Attending @Scalarconf in #Warsaw? Don't miss out on: “Exploring Build Caching: A Practical Overview” 👇 https://lnkd.in/dZnB7wuD Presented by Martin Duhem from the #Gradle #Develocity team, you’ll learn what we’re doing to accelerate #sbt builds for #Scala developers! -- tags: #DPE #DeveloperProductivityEngineering #DevProd #DevX #buildcache

The Kubernetes Pod Lifecycle is crucial for ensuring the availability and stability of containerized applications. It encompasses phases like Pending, Running, Succeeded, Failed, and Unknown. Understanding and managing this lifecycle helps orchestrate container deployments, scale resources, handle failures, and maintain desired states, ensuring efficient container management and reliable application operation in a dynamic, distributed environment.

🐳𝟭𝟬𝟬 𝗗𝗼𝗰𝗸𝗲𝗿 𝗜𝗻𝘁𝗲𝗿𝘃𝗶𝗲𝘄 𝗤𝘂𝗲𝘀𝘁𝗶𝗼𝗻𝘀 & 𝗔𝗻𝘀𝘄𝗲𝗿𝘀 🐳 Hello #DevOps People, Here is a document of 100 docker interview questions & answers. Check it out. Connect With me For more such stuff at Aisha Shaik #Docker #Containerization #DevOps #Microservices #Kubernetes #ContainerOrchestration #CI/CD #DevOpsEngineer #SoftwareDevelopment #CloudComputing #InfrastructureAsCode #ContinuousIntegration #ContinuousDeployment #ContainerSecurity #devopsjobs #devopscommunity #devopsshack

Docker cheat sheet. Refer before interview. #docker #devops #devopsengineer #dockercontainer #dockers #notes #awsdevops

Need a website created or do you need your database integrated? Visit us at inovitytech.com #customsoftware #softwaredevelopment #customapp #tailoredsoftware #agiledevelopment #digitaltransformation #techinnovation #codinglife #codecrafting #DevOps

Kubernetes Pod Lifecycle Phases 🚀 Lets understand the phases with a real-world example. The pod's phase gives a brief update on the pod's current status. A quick way to understand what's happening with the pod. In pods lifecycle, we have - Pod Phases - Pod Conditions - Container Status In this post, we will look at only Pod Phases. To understand the concepts better let's assume a multi-container pod with the following - An init container to fetch an API secret in the runtime. - container-01 (java-api) runs the Java application - container-02 (log-reader) fetches the application logs, and sends them to a log forwarder. We will understand the pod lifecycle by understanding what happens when we deploy the pod with the above requirements. Here is a short blog that explains the phases 𝗣𝗼𝗱 𝗣𝗵𝗮𝘀𝗲𝘀 𝗕𝗹𝗼𝗴: https://lnkd.in/giuUFKAg In the next K8s blog, we will look at Pod Conditions in detail. To get a notification on my next K8s post, hit the 🔔 on my profile. Also, Share it with your friends who are interested in learning kubernetes. #devops #kubernetes #devopsengineer