SRE Starter Kit for Linux Kubernetes Automation

We literally used sudo in the last lecture… And no one asked why. That’s the problem. Most people learning Linux for DevOps don’t actually learn things… They just follow along. Run this command. Copy that step. It works - so they move on. Until one day… Production says: Permission denied. And suddenly: – Commands stop working – Logs are inaccessible – Panic starts Because now it’s not about what to type It’s about who you are in the system User? sudo user? root? That difference decides everything. I’ve seen engineers who know Docker, Kubernetes, CI/CD… But still get stuck on something as basic as privileges. Not because it’s hard - But because no one explained it properly. So instead of just using sudo again… We stopped. And broke it down: – What actually happens when you run sudo – Why switching to root is risky – When to use su vs sudo in real systems Because DevOps is not about running commands. It’s about understanding control. And in Linux… control starts with privileges. If you’ve ever used sudo without thinking… You should probably watch this one. Link in comments 👇 #Linux #DevOps #CloudComputing #SystemDesign #AWS #DevOpsEngineer #LinuxCommands #TechCareers #Programming

🚀 Day 3/30 – DevOps Journey Today I focused on understanding Linux file permissions, which play a critical role in system security and access control. 💡 Key Learnings: Types of permissions: Read (r), Write (w), Execute (x) Permission groups: User, Group, Others Understanding permission format (e.g., rwxr-xr-x) Using chmod to modify permissions Basics of chown for ownership management 💻 Hands-on: Created files and checked permissions using ls -l Modified permissions using chmod Observed how access changes based on permission settings 📌 Key Takeaway: Linux permissions are essential for securing systems and managing user access in real-world DevOps environments. 🔗 GitHub (Day 3 work): https://lnkd.in/gJVDpbRF Step by step, building strong fundamentals 💪 #DevOps #Linux #Permissions #AWS #LearningJourney #30DaysChallenge

🚀 Day 4/30 – DevOps Journey Today I explored advanced Linux commands that are very useful in real-world DevOps tasks. 💡 Key Learnings: grep command to search text inside files Pipe (|) to combine multiple commands cat command to read file content echo command to create and modify files 🔍 Also explored: grep options like -i (ignore case), -n (line numbers) Filtering and processing command outputs using pipes 💻 Hands-on: Created files and added content using echo Searched specific words using grep Combined commands to filter output efficiently 📈 How I Improved: Gained better understanding of command-line usage Learned how to combine commands instead of running them separately Improved my ability to analyze file content quickly Built confidence working with Linux terminal 📌 Key Takeaway: Combining commands using pipes makes Linux very powerful for tasks like log analysis, debugging, and automation. 🔗 GitHub (Day 4 work): https://lnkd.in/gJVDpbRF Learning step by step and improving every day 💪 #DevOps #Linux #Automation #Cloud #LearningJourney #30DaysChallenge

🚨 The first time I opened a Linux server… I saw folders like `/bin`, `/etc`, `/var`, `/home` and thought: “What is all this? And why is everything starting with `/`?” 😅 That confusion led me to learn something very important for DevOps. 💡 𝘋𝘢𝘺 9 𝘰𝘧 𝘮𝘺 𝘋𝘦𝘷𝘖𝘱𝘴 𝘑𝘰𝘶𝘳𝘯𝘦𝘺 Today I learned about the 𝗟𝗶𝗻𝘂𝘅 𝗙𝗶𝗹𝗲 𝗦𝘆𝘀𝘁𝗲𝗺 — the structure that organizes everything inside a Linux system. --- 📖 Think of it like a 𝗺𝗮𝗽 𝗼𝗳 𝘁𝗵𝗲 𝗲𝗻𝘁𝗶𝗿𝗲 𝗼𝗽𝗲𝗿𝗮𝘁𝗶𝗻𝗴 𝘀𝘆𝘀𝘁𝗲𝗺. In Linux, everything starts from a single root directory: 👉 `/` (root) From there, the system branches into different directories, each with a specific purpose. --- Here are some important ones I learned today: 📁 /𝗯𝗶𝗻 Contains essential command binaries like `ls`, `cp`, `mv`. 📁 /𝗲𝘁𝗰 Stores system configuration files. 📁 /𝗵𝗼𝗺𝗲 Personal directories for users. 📁 /𝘃𝗮𝗿 Contains logs, cache, and variable data. 📁 /𝘂𝘀𝗿 Stores system programs and utilities. 📁 /𝘁𝗺𝗽 Temporary files used by applications. --- 🚀 𝘞𝘩𝘺 𝘵𝘩𝘪𝘴 𝘮𝘢𝘵𝘵𝘦𝘳𝘴 𝘪𝘯 𝘋𝘦𝘷𝘖𝘱𝘴? Because when you manage servers, deploy applications, or troubleshoot issues… You constantly interact with these directories. Knowing 𝘄𝗵𝗲𝗿𝗲 𝘁𝗵𝗶𝗻𝗴𝘀 𝗹𝗶𝘃𝗲 𝗶𝗻 𝗟𝗶𝗻𝘂𝘅 saves a lot of time when debugging systems. --- 🔥 𝘔𝘺 𝘣𝘪𝘨𝘨𝘦𝘴𝘵 𝘳𝘦𝘢𝘭𝘪𝘻𝘢𝘵𝘪𝘰𝘯 𝘵𝘰𝘥𝘢𝘺: Linux is not random. Every directory has a 𝘀𝗽𝗲𝗰𝗶𝗳𝗶𝗰 𝗿𝗼𝗹𝗲 𝗶𝗻 𝗸𝗲𝗲𝗽𝗶𝗻𝗴 𝘁𝗵𝗲 𝘀𝘆𝘀𝘁𝗲𝗺 𝗼𝗿𝗴𝗮𝗻𝗶𝘇𝗲𝗱 𝗮𝗻𝗱 𝘀𝘁𝗮𝗯𝗹𝗲. --- 📌 𝘚𝘮𝘢𝘭𝘭 𝘬𝘯𝘰𝘸𝘭𝘦𝘥𝘨𝘦 𝘭𝘪𝘬𝘦 𝘵𝘩𝘪𝘴 𝘣𝘦𝘤𝘰𝘮𝘦𝘴 𝘱𝘰𝘸𝘦𝘳𝘧𝘶𝘭 𝘸𝘩𝘦𝘯 𝘸𝘰𝘳𝘬𝘪𝘯𝘨 𝘸𝘪𝘵𝘩 𝘴𝘦𝘳𝘷𝘦𝘳𝘴 𝘢𝘯𝘥 𝘤𝘭𝘰𝘶𝘥 𝘪𝘯𝘧𝘳𝘢𝘴𝘵𝘳𝘶𝘤𝘵𝘶𝘳𝘦. And that’s exactly what DevOps engineers deal with daily. --- 💬 𝘋𝘦𝘷𝘖𝘱𝘴 𝘦𝘯𝘨𝘪𝘯𝘦𝘦𝘳𝘴 𝘩𝘦𝘳𝘦 — Which Linux directory confused you the most when you started? 😅 --- Learning step by step 🚀 #DevOps #Linux #LinuxFileSystem #LearningInPublic #DevOpsInsiders #TechJourney

Headline: 🚀 Day 15 of My DevOps Roadmap: 🚀 Linux Learning Journey – Day 15 🧠 Memory Leak? Or Just Linux Being Smart? 👇 Many engineers panic seeing low free memory ❌ But in Linux, that’s often normal. Let’s break it down properly 👇 ⚙️ Step 1: Check Memory free -h 👉 Focus on: • available (not free!) • swap usage 🔍 Step 2: Find Top Consumers top → Press Shift + M OR ps -eo pid,cmd,%mem --sort=-%mem | head 📈 Step 3: Detect Memory Leak 👉 Signs: • Memory keeps increasing over time • Process RES keeps growing • Swap usage rising ⚠️ Common Confusion • High cache ≠ problem • Linux uses RAM for performance 🔥 Real Problem Indicators • Low available memory • High swap usage • OOM (Out Of Memory) kills 🛠️ Step 4: Action kill -9 <PID> (temporary fix) Optional (careful): sync; echo 3 > /proc/sys/vm/drop_caches 💡 Pro Tip If swap is used heavily → system will become very slow 📌 Save this — very common interview + real-world issue 📌 Next post: Disk I/O Bottleneck (most ignored problem!) #Linux #DevOps #SRE #MemoryLeak #SystemDesign #Debugging #Cloud

🚀 Day 12: Linux Internals for DevOps Engineers (Advanced) 👉 Disk Issues in Production (Not as simple as you think) Most people think: ❌ Disk full → delete files → done But real production issues are more complex. Today I explored how engineers actually debug disk-related failures. 📌 What I learned: 🔹 `df -h` shows disk usage 🔹 `du -sh` helps trace large directories 🔹 Sometimes deleted files still occupy space (hidden usage) 🔹 Log rotation is critical to prevent repeated failures 💡 Real Scenario: Disk shows 100% usage… But you can’t find large files. Why? 👉 Because deleted files are still held by running processes. Solution: ✔ Use `lsof | grep deleted` ✔ Restart the process This is something most beginners don’t know. 🧠 Question for you: Have you ever faced a situation where disk was full but you couldn’t find the files causing it? 👇 Would love to know your experience! 🎯 Learning Goal: To debug storage issues deeply and prevent recurring failures. 📅 Day 13 Tomorrow: Networking Basics (IP, Ports, DNS) Let’s keep going deeper 🚀 #DevOps #Linux #SRE #Storage #CloudComputing #SoftwareEngineering #TechLearning #LearningInPublic #ITCareers #EngineeringMindset #CareerGrowth #ProductionIssues

Day 6 of becoming a DevOps Engineer Navigating the Linux Filesystem - A Must-Know for Every Tech Learner In Linux, everything is organized—and everything lives somewhere for a reason. Understanding the Linux filesystem isn’t just theory. It’s a core skill for system administration, troubleshooting, and working confidently in any Linux environment. Here’s a simplified breakdown: 🔹 Core System Directories / – The root of everything. Every file and directory starts here. /bin & /usr/bin – Essential command tools like ls, cp, cat. /sbin & /usr/sbin – System-level commands (used for admin tasks). /etc – Configuration files for the system and applications. /home – Personal space for users. /root – Home directory for the superuser. /boot – Files required to start the system. 🔹 Dynamic & System Directories /dev – Represents hardware devices. /proc & /sys – Real-time system and process information. /var – Frequently changing data like logs and web files. /tmp – Temporary files (often cleared on reboot). /opt – Optional or third-party software. /lib & /usr/lib – Shared libraries for programs. /media & /mnt – Mount points for external drives. /run – Runtime system data since last boot. Key Insight: The Linux filesystem follows a structured standard, which means once you understand it, you can navigate almost any Linux system with confidence. For me, this is more than just learning directories… It’s about building a solid foundation for DevOps and Cloud Engineering. #BuildInPublic #TechJourney #Linux #DevOps #CloudComputing #TechInAfrica #TechLearning #SystemAdministration #ContinuousLearning #TSAcademy #30DaysOfLearning

🚀 From Zero to 60+ Linux Commands — Since the end of March and throughout April, I focused on building a strong foundation in Linux and mastered top 10 services of AWS — from basics to advanced concepts. 🔧 Here are some of the most practical commands I worked with: 📁 File Management: ls, cd, pwd, cp, mv, rm, touch, mkdir, rmdir 🔐 Permissions & Ownership: chmod, chown, chgrp, umask 👤 User Management: useradd, usermod, userdel, passwd, whoami, id 📊 Monitoring & System Info: top, htop, ps aux, ps -ef, df -h, du -sh, free -m, uptime, dmesg, lsblk, lshw ⚙️ Service Management (Systemctl): systemctl start, systemctl stop, systemctl restart, systemctl status 📦 Archiving & Compression: tar -cvf, tar -xvf 🔍 Search & Text Processing: grep, find, locate, cat, less, head, tail, wc ❌ Process Control: kill, kill -9 💡 This journey helped me understand how Linux powers real-world systems, especially in DevOps and Cloud environments. ❓ Question for Linux/System Admins: When debugging an OOM (Out Of Memory) issue, I’ve been using grep on logs (like dmesg or /var/log/syslog) to find OOM kill messages. 👉 Is this the right approach in real-world scenarios, or are there better tools/commands you prefer? Would love to learn how it’s handled in production environments 🙌 Big Thanks to Vikas Ratnawat CloudDevOpsHub Community for mentoring. 😀 Tomorrow I will be sharing my project of Automation & shell scripting deployed on google cloud. Consistency over everything. Still learning, still building. #Linux #DevOps #CloudComputing #ShellScripting #Automation #LearningJourney #TechSkills

🚀 Brushing Up My DevOps Foundations: Linux Commands That Power Everything As part of strengthening my DevOps skill set, I’ve been revisiting one of the most fundamental yet powerful tools in the ecosystem — Linux. Understanding Linux commands is not just about navigating a system; it's about gaining control, efficiency, and deeper insight into how infrastructure works behind the scenes. Here are a few essential commands I’ve been focusing on: 🔹 ls, cd, pwd – Navigating directories 🔹 grep, find – Searching like a pro 🔹 chmod, chown – Managing permissions 🔹 top, ps – Monitoring system performance 🔹 tar, zip – Handling archives 💡 What I’m realizing is that mastering these basics builds a strong foundation for tools like Docker, Kubernetes, and CI/CD pipelines. Consistency is key — small daily improvements lead to big results. Excited to keep learning and growing in the DevOps journey! #DevOps #Linux #LearningJourney #CloudComputing #Upskilling #TechCareers

🚀 Day 2 of #100DaysOfDevOps — Diving into Linux Fundamentals Today, I strengthened my foundation by exploring one of the most essential technologies in the DevOps world — Linux 🐧 🔹 What is Linux? Linux is an open-source, Unix-like operating system known for its stability, security, and flexibility. It powers everything from personal systems to enterprise infrastructure and cloud environments. 🔹 Why Linux for Servers? Linux is the backbone of modern servers because it is: ✔️ Highly secure and reliable ✔️ Lightweight and efficient ✔️ Scalable for large systems ✔️ Strongly supported by the open-source community ✔️ Perfectly suited for cloud and containerized environments 🔹 Users in Linux Understanding user roles is crucial for system security: 👤 Root User – Full administrative control 👤 Regular Users – Limited access for daily tasks 👤 sudo – Grants temporary administrative privileges 👥 Groups – Simplifies permission management 💻 Key Linux Commands I Practiced Today 🔹 System Commands (Managing the OS) Commands like uname, hostname, and uptime help monitor system info. whoami, id, and pwd identify users and directories. File operations using ls, cd, mkdir, rm, and cp are fundamental for navigation and management. Tools like top, ps, and kill are essential for process management. 🔹 Hardware Commands (Understanding System Resources) Commands such as lscpu, lsblk, and free -h provide insights into CPU, storage, and memory. lspci and lsusb detect connected devices. dmidecode and smartctl help analyze hardware health and system-level details. 🔹 Switch/Network Commands (Connectivity & Networking) ip -a and ip -r help manage IP addresses and routing. ping and traceroute are used for connectivity testing. netstat and ss display network connections and ports. Tools like curl, wget, nslookup, and dig are essential for network communication and troubleshooting. 🧠 Key Takeaways ✔️ Everything in Linux is treated as a file ✔️ Permissions (read, write, execute) control access ✔️ The shell is powerful for automation ✔️ Linux is the core of DevOps and modern infrastructure 🔥 Consistency is key — one step closer to mastering DevOps! #DevOps #Linux #100DaysOfDevOps #CloudComputing #LearningInPublic #TechJourney #SystemAdministration #Networking #Automation #flm