sameera pathum’s Post

15 Kubernetes Commands for DevOps Fire Fighters Purely focused on troubleshooting. 𝙠𝙪𝙗𝙚𝙘𝙩𝙡 𝙚𝙭𝙚𝙘 -𝙞𝙩 [𝙥𝙤𝙙-𝙣𝙖𝙢𝙚] -- /𝙗𝙞𝙣/𝙗𝙖𝙨𝙝 - When you need to access a pod shell  𝙠𝙪𝙗𝙚𝙘𝙩𝙡 𝙡𝙤𝙜𝙨 [𝙥𝙤𝙙-𝙣𝙖𝙢𝙚] - When you need to fetch pod logs  𝙠𝙪𝙗𝙚𝙘𝙩𝙡 𝙜𝙚𝙩 𝙚𝙫𝙚𝙣𝙩𝙨- When you need to check recent events    𝙠𝙪𝙗𝙚𝙘𝙩𝙡 𝙩𝙤𝙥 𝙥𝙤𝙙𝙨/𝙣𝙤𝙙𝙚𝙨 - When you need to monitor pod/node resource usage  𝙠𝙪𝙗𝙚𝙘𝙩𝙡 𝙙𝙚𝙨𝙘𝙧𝙞𝙗𝙚 𝙥𝙤𝙙 [𝙥𝙤𝙙-𝙣𝙖𝙢𝙚]/𝙣𝙤𝙙𝙚 [𝙣𝙤𝙙𝙚-𝙣𝙖𝙢𝙚] - When you need detailed pod/node information  𝙠𝙪𝙗𝙚𝙘𝙩𝙡 𝙥𝙤𝙧𝙩-𝙛𝙤𝙧𝙬𝙖𝙧𝙙 [𝙥𝙤𝙙-𝙣𝙖𝙢𝙚] [𝙡𝙤𝙘𝙖𝙡-𝙥𝙤𝙧𝙩]:[𝙥𝙤𝙙-𝙥𝙤𝙧𝙩] - When you need to forward a port to a pod  𝙠𝙪𝙗𝙚𝙘𝙩𝙡 𝙘𝙥 [𝙥𝙤𝙙-𝙣𝙖𝙢𝙚]:[𝙥𝙖𝙩𝙝] [𝙡𝙤𝙘𝙖𝙡-𝙥𝙖𝙩𝙝]- When you need to copy files from pod to local  𝙠𝙪𝙗𝙚𝙘𝙩𝙡 𝙧𝙤𝙡𝙡𝙤𝙪𝙩 𝙨𝙩𝙖𝙩𝙪𝙨 𝙙𝙚𝙥𝙡𝙤𝙮𝙢𝙚𝙣𝙩 [𝙙𝙚𝙥𝙡𝙤𝙮𝙢𝙚𝙣𝙩-𝙣𝙖𝙢𝙚] - When you need to check deployment rollout status  𝙠𝙪𝙗𝙚𝙘𝙩𝙡 𝙙𝙧𝙖𝙞𝙣 [𝙣𝙤𝙙𝙚-𝙣𝙖𝙢𝙚] - When you need to prepare a node for maintenance  𝙠𝙪𝙗𝙚𝙘𝙩𝙡 𝙘𝙤𝙧𝙙𝙤𝙣 [𝙣𝙤𝙙𝙚-𝙣𝙖𝙢𝙚] - When you need to mark a node as unschedulable  𝙠𝙪𝙗𝙚𝙘𝙩𝙡 𝙪𝙣𝙘𝙤𝙧𝙙𝙤𝙣 [𝙣𝙤𝙙𝙚-𝙣𝙖𝙢𝙚] - When you need to mark a node as schedulable    𝙠𝙪𝙗𝙚𝙘𝙩𝙡 𝙩𝙖𝙞𝙣𝙩 𝙣𝙤𝙙𝙚𝙨 [𝙣𝙤𝙙𝙚-𝙣𝙖𝙢𝙚] 𝙠𝙚𝙮=𝙫𝙖𝙡𝙪𝙚:𝙉𝙤𝙎𝙘𝙝𝙚𝙙𝙪𝙡𝙚 - When you need to taint a node  𝙠𝙪𝙗𝙚𝙘𝙩𝙡 𝙚𝙙𝙞𝙩 [𝙧𝙚𝙨𝙤𝙪𝙧𝙘𝙚] [𝙣𝙖𝙢𝙚] - When you need to edit a resource configuration  𝙠𝙪𝙗𝙚𝙘𝙩𝙡 𝙙𝙚𝙨𝙘𝙧𝙞𝙗𝙚 𝙨𝙚𝙧𝙫𝙞𝙘𝙚 [𝙨𝙚𝙧𝙫𝙞𝙘𝙚-𝙣𝙖𝙢𝙚]/𝙞𝙣𝙜𝙧𝙚𝙨𝙨 [𝙞𝙣𝙜𝙧𝙚𝙨𝙨-𝙣𝙖𝙢𝙚]/𝙝𝙥𝙖 [𝙝𝙥𝙖-𝙣𝙖𝙢𝙚] - When you need detailed service/ingress/HPA information  𝙠𝙪𝙗𝙚𝙘𝙩𝙡 𝙜𝙚𝙩 𝙙𝙖𝙚𝙢𝙤𝙣𝙨𝙚𝙩𝙨- When you need to check daemonset status  +1 bonus:   𝙠𝙪𝙗𝙚𝙘𝙩𝙡 𝙜𝙚𝙩 𝙨𝙚𝙘𝙧𝙚𝙩𝙨 - When you need to check secret status Running commands is a simple act. What you infer and take action on determines the speed of a fix. 🔁 Consider a REPOST if this is helpful. -- I'm Govardhana Miriyala Kannaiah and I run a digital and cloud consulting firm, NeuVeu. Trusted by Stanford University, Hearst Corporation and 15+ clients in 12+ countries over the last year. If you are a business looking for help, you can schedule a free business consultation call with me (calendly link in the bio)

𝗝𝗲𝗻𝗸𝗶𝗻𝘀 𝗦𝗲𝗿𝗶𝗲𝘀: 𝗗𝗮𝘆 𝟬𝟮: Understanding Jenkins HA 🚀 There is no direct way of setting up Jenkins in High availability mode due to how Jenkins manages its data. Jenkins manages its data in a flat-file (xml), and you can have only one instance of the master node that can read the Jenkins data. Because of which, running multiple replicas of the Jenkins master in an active-active configuration (where all replicas are actively processing jobs) is not officially supported. For example, if you try to configure multiple master nodes with a shared volume, you will have inconsistent reads and writes that lead to unstable Jenkins. 𝗡𝗼𝘁𝗲: In cloudbees enterprise Jenkins active-active setup is supported. This blog will discuss setting up a Highly available Jenkins using the open-source version. 𝗗𝗲𝘁𝗮𝗶𝗹𝗲𝗱 𝗕𝗹𝗼𝗴: https://lnkd.in/g8AjmY_M PS: ♻️ Dont forget to repost! and share it with DevOps community Have anything to add? Discuss in the comments #devops #jenkins #practicaldevops

𝐇𝐨𝐰 𝐂𝐈𝐂𝐃 𝐏𝐈𝐩𝐞𝐥𝐢𝐧𝐞 𝐰𝐨𝐫𝐤𝐬❗ In today's fast-paced world of software development, success is synonymous with efficiency, rapid deployment, and minimal disruptions. CI/CD pipelines serve as the catalyst for achieving agile development and smoother software delivery. 🔗 𝐖𝐡𝐚𝐭 𝐢𝐬 𝐂𝐈/𝐂𝐃❓ CI/CD, an acronym for Continuous Integration and Continuous Deployment, represents a holistic approach aimed at automating the integration of code changes and their seamless deployment into production. This ensures that your software is in a state of perpetual readiness for deployment, emphasizing incremental updates over unwieldy, error-prone releases. 🛠 𝐇𝐨𝐰 𝐃𝐨𝐞𝐬 𝐚 𝐂𝐈/𝐂𝐃 𝐏𝐢𝐩𝐞𝐥𝐢𝐧𝐞 𝐖𝐨𝐫𝐤❓ Continuous Integration (CI): 🎯Developers craft code and seamlessly upload it to a shared repository. Continuous Deployment (CD): 🎯Once the code emerges unscathed from the rigorous CI phase, it's primed for deployment. ⚙️ 𝐊𝐞𝐲 𝐂𝐨𝐦𝐩𝐨𝐧𝐞𝐧𝐭𝐬 𝐨𝐟 𝐚 𝐂𝐈/𝐂𝐃 𝐏𝐢𝐩𝐞𝐥𝐢𝐧𝐞: ✅Source Control Management (SCM): This is the digital heart where developers store their code, often utilizing Git-based repositories such as GitHub or GitLab. ✅Build Tools: These are the skilled artisans that compile, package, and optimize your code for deployment. Popular options include Jenkins, Travis CI, and CircleCI. ✅Artifact Repositories: Where the precious gems of your code, like Docker images and application binaries, are safely stored for deployment. ✅Deployment Tools: The automation wizards that wave their magic wands to dispatch your code to different environments, be it Kubernetes, Docker Swarm, or serverless platforms. ✅Testing Automation: A battalion of unit, integration, and end-to-end tests that vigilantly safeguard your code's quality and functionality. 🌟 Benefits of CI/CD: ✅Faster Delivery: Smaller, more frequent releases mean quicker feature updates and bug fixes. ✅Enhanced Collaboration: Developers can simultaneously work on different features, creating harmonious, conflict-free collaboration. 𝐂𝐥𝐨𝐮𝐝𝐚𝐢𝐫𝐲 𝐂𝐥𝐨𝐮𝐝𝐜𝐡𝐚𝐫𝐭 can help you design, manage, and discuss multi-cloud architectures in a user-friendly and collaborative way. It offers a visual interface to: ✔️ Design your cloud architecture with drag-and-drop functionality. ✔️ ️Collaborate with your team members on the architecture. ✔️ Visualize your cloud architecture in real-time and simplify the development process! 𝐒𝐢𝐠𝐧 𝐮𝐩 𝐟𝐨𝐫 𝐭𝐡𝐞 𝐂𝐥𝐨𝐮𝐝𝐜𝐡𝐚𝐫𝐭 𝐁𝐞𝐭𝐚 𝐕𝐞𝐫𝐬𝐢𝐨𝐧 𝐭𝐨𝐝𝐚𝐲❗ https://lnkd.in/e2zNP8Zp #softwaredevelopment #softwareengineering #kubernetes #devops #cloudairy

Jenkins 💡

🔧 𝗗𝗶𝘃𝗲 𝗶𝗻𝘁𝗼 𝟮𝟬𝟬 𝗘𝘀𝘀𝗲𝗻𝘁𝗶𝗮𝗹 𝗔𝗻𝘀𝗶𝗯𝗹𝗲 𝗜𝗻𝘁𝗲𝗿𝘃𝗶𝗲𝘄 𝗤𝘂𝗲𝘀𝘁𝗶𝗼𝗻𝘀 𝘄𝗶𝘁𝗵 𝗗𝗲𝘁𝗮𝗶𝗹𝗲𝗱 𝗦𝗼𝗹𝘂𝘁𝗶𝗼𝗻𝘀! 🚀 Master Configuration Management and Automation with ease. Perfect for acing your next DevOps interview! 🌟 #Ansible #DevOps #InterviewPrep #Automation #ConfigurationManagement #TechTips #JobReady #LearnAndGrow #ITCareers #SkillUp 💡📘 Follow Amisha Singh 👈🚶♀️