"You devs just write your code and think everything is done. You don't understand what happens after." That was my CTO, he was complaining after we had fixed a virtual machine that had run out of storage space. How had it run out of storage space? Well, I had created multiple log channels, each one writing to their own daily log file, and just left them there to accumulate. I killed the VM by having hundreds of thousands of log files 1MB or less, whoops. When I was developing I didn't think about tidying up the files, even telling anyone about the log files, this little 170kb file won't harm anything right? Every process had it's own log channel and daily log file so if anything does go wrong someone could find out exactly what it was easily. I was happily making a mountain out of small stones blissfully unaware of the problem I was creating. Obviously, we need log files, but it hadn't occurred to me that they would take up space, and eventually use all the space and crash the VM. I had done logging without any clean up. It’s like installing a toilet with no plumbing and acting surprised when the room smells funny. This is why having infrastructure knowledge and skills is so valuable. It changes how you think about the entire process of development, I see things differently now. Having infrastructure knowledge means that I make better architectural decisions at the start of a project. It means I'm a better team mate understanding another's role and making their job easier. Most importantly, it means not walking in to work and having an important application down, everyone asking why, and being pressured to fix it ASAP. I have a cron job that zips and moves the log files so they can be deleted now, but I wish I had thought of that from the start. Don't work in a silo, see the big picture, it will save your day.

This post is for everyone who's still on levels 1 to 3. Go on, say hello :-) Anyone who's level 4 or higher is only allowed to use the reply function. Let's see if this works here -Mischa

Time flies when you're having fun! The Free Community has already grown to 4K members in just a few months. I want to thank you for all the appreciation and positive feedback you've given on the free courses. We've had amazing contributors this month like @Cedric J, @Deleted, @Ilyas Elhallaoui , @Christian Herrera, @Gift Phiri and @Aung Ko Htet. Keep it up! The KubeCraft community has likewise grown and is also nearing its 500 Member cap. Looks like just a few weeks at most. 2025 will be the year of us DevOps Engineers! Keep learning and chasing your dreams, Mischa

Welcome to KubeCraft. The community where (aspiring) DevOps engineers become undeniable. You are not here to collect endless tutorials. You are here to get hired, build real skills, and move forward with people who want the same outcome. Inside KubeCraft, we share one mission: Become a high paid DevOps engineer while solving real world problems together trough DevOps Craftsmanship. You are no longer doing this alone. You are part of a focused group built to push your growth every step of the way. We help you to: • Build real world DevOps skills through projects, challenges, and proof of work • Land your first DevOps role or level up your current one • Stay accountable inside a community that expects action, not excuses You are in the right place if: • You want to become a DevOps or Cloud engineer and are passionate about this craft • You are willing to do the work, ask questions, and support others • You want a real DevOps environment, not another passive course platform Follow these steps: 1. Post your introduction below (and level up to level 2+ fast) 2. Like & reply to other introductions 3. Your onboarding shows how this community works and what is expected 4. You will see exactly how to create momentum fast with the Welcome to the KubeCraft, Crafter. Let’s get to work.