Day 4 cloud challenge: Was manually creating OS images like a caveman 🦕 Thought about automating with bash scripts but that's just trading one headache for another - different package managers, brittle dependencies, zero error handling. One Ubuntu script breaks on CentOS and

Day 5 of infrastructure challenge 🧵 Started with a "simple" 3-node cluster. Now I'm juggling: - Packer - Ansible - Terraform - Remote state - Self-hosted GH Actions - Public docs It's a beautiful mess. Nothing works together yet. Sometimes the best learning happens when

AWS Lambda remote debugging is finally here and I'm embarrassingly excited about it No more console.log debugging hell. No more dependent on cloudwatch logs. Just actual breakpoints like a civilized developer. RIP to all those Friday afternoons lost to deploy-log-guess-repeat

Day 6 update: spent the entire day fighting with GitHub Actions 🥲 Self-hosted runners + local cluster = way more complexity than expected Still nothing works properly but hey, at least I'm consistent Weekend mission: make something - anything - actually work 🤞 #DevOps

🚀 Day 7 of Cloud Challenge: Terraform State Management Deep Dive Just spent the day setting up proper remote state infrastructure and it's a game-changer! Built an S3 bucket for state storage and DynamoDB table for state locking using a bootstrap Terraform config. Then used

🚀 Day 8 of Challenge: Integrating GitHub Actions for Seamless CI/CD! Building off yesterday's remote backend (S3 + DynamoDB), I spun up a fresh Terraform project and wired it to GitHub Actions. Now, PRs auto-run 'terraform plan' to preview changes, and merges trigger

At this point I’m convinced that finding great aerospace engineers is 10x harder than building the damn thing. Nobody uses/updates their LinkedIn. If you know someone who’s actually cracked, tell them to hit me up or tag them. We’re building crazy stuff LAT Aerospace.

🧵 Thread: How a simple SSD failure turned into a 4-day masterclass in Linux storage fundamentals My 3-node Proxmox cluster wouldn't boot. "Probably just needs a restart," I thought. Spoiler: It didn't. #HomeLab #Linux #TechLearning

Day 10 of #ReplicatingCloudStackOnDesk: Finally got on-demand GitHub Actions runners spinning up on my home Proxmox setup via Cloudflare Tunnels & Packer. Chicken-and-egg hell, sounds simple but nightmare to setup, finally got it working end to end. had planned for a much

Was watching this and Talk Football HD asked Ranjit Bajaj despite so many challenges why are you doing all this efforts and Ranjit ji answered someone has to do it to show that it's possible and it'll open the floodgates.

Vishakh Ranotra

AWS just announced expanded Cilium support for EKS Hybrid Nodes Here's who this is for: • Teams running Kubernetes workloads across AWS + on-premises • Organizations needing advanced networking (BGP, VXLAN, network policies) • Companies wanting AWS enterprise support for

Hot take: You don't truly know a command until you've read its `man` page multiple times First read: "Ok I get the basics" Second read: "Wait, there are THESE options?" Third read: "Holy shit, I can do THAT?" Fourth read: "I've been using this wrong for years" `man grep` hits

🔧 PSA: That #!/bin/bash at the top of your shell scripts isn't optional decoration. Without it: ❌ Script might use wrong interpreter ❌ Bash features could fail silently ❌ Different behavior across systems With it: ✅ Guaranteed bash execution ✅ Consistent results

🔧 PSA: That #!/bin/bash at the top of your shell scripts isn't optional decoration. Without it: ❌ Script might use wrong interpreter ❌ Bash features could fail silently ❌ Different behavior across systems With it: ✅ Guaranteed bash execution ✅ Consistent results

🔧 PSA: That #!/bin/bash at the top of your shell scripts isn't optional decoration. Without it: ❌ Script might use wrong interpreter ❌ Bash features could fail silently ❌ Different behavior across systems With it: ✅ Guaranteed bash execution ✅ Consistent results

Deepak M Nadiger You & few others have set some crazy benchmarks.