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.

Wishing everyone in KubeCraft community a strong, focused and supportive 2026. Every small win you share pushes the whole group forward 💪 Let’s kick it off with this week’s KubeQuest. ⚔️ 𝗞𝘂𝗯𝗲𝗤𝘂𝗲𝘀𝘁 𝗠𝗼𝗻𝗱𝗮𝘆 New week. New focus. New progress. We keep it simple 👇 𝗦𝗧𝗘𝗣 𝟭: 𝗪𝗲𝗲𝗸𝗹𝘆 𝗚𝗼𝗮𝗹𝘀 (𝗠𝗼𝗻𝗱𝗮𝘆) Post your 1–3 DevOps goals for the week in the comments under this post 𝗦𝗧𝗘𝗣 𝟮: 𝗨𝗽𝗱𝗮𝘁𝗲 & 𝗪𝗶𝗻 (𝗙𝗿𝗶/𝗦𝘂𝗻) Before the week ends, reply to your own comment with: - Your status update - Your biggest win Whether everything is completed or not, showing up and reporting back is what matters. 🗓️ 𝗧𝗶𝗺𝗲𝗹𝗶𝗻𝗲: Weeks run from Monday to Sunday 👉 𝗘𝘅𝗮𝗺𝗽𝗹𝗲 𝗦𝘂𝗯𝗺𝗶𝘀𝘀𝗶𝗼𝗻: See the example below. Each week we'll create a fresh new post to keep the momentum going. 🏆 𝗪𝗲𝗲𝗸𝗹𝘆 𝘄𝗶𝗻: Each week one member who posted and returned gets a community shoutout. Post your goals today and come back this weekend with proof. Good luck this week 🔥

Good afternoon Crafters! As we’re closing out 2025, one thing really stands out: the people who keep showing up Once again, @Adeyemi Ojo did exactly that. Second week in a row where he did what this is really about. Goals set. Work done. Update posted ✅ Nothing fancy, just consistent progress and good follow-through. That’s how you get better over time. Nice one @Adeyemi Ojo , thanks for setting the tone again 🙌 ⚔️ 𝗞𝘂𝗯𝗲𝗤𝘂𝗲𝘀𝘁 𝗠𝗼𝗻𝗱𝗮𝘆 𝗶𝘀 𝗹𝗶𝘃𝗲 New week. New focus. New progress. We keep it simple 👇 𝗦𝗧𝗘𝗣 𝟭: 𝗪𝗲𝗲𝗸𝗹𝘆 𝗚𝗼𝗮𝗹𝘀 (𝗠𝗼𝗻𝗱𝗮𝘆) Post your 1–3 DevOps goals for the week in the comments under this post 𝗦𝗧𝗘𝗣 𝟮: 𝗨𝗽𝗱𝗮𝘁𝗲 & 𝗪𝗶𝗻 (𝗙𝗿𝗶/𝗦𝘂𝗻) Before the week ends, reply to your own comment with: - Your status update - Your biggest win Whether everything is completed or not, showing up and reporting back is what counts. 🗓️ 𝗧𝗶𝗺𝗲𝗹𝗶𝗻𝗲: Weeks run from Monday to Sunday 👉 𝗘𝘅𝗮𝗺𝗽𝗹𝗲 𝗦𝘂𝗯𝗺𝗶𝘀𝘀𝗶𝗼𝗻: See the example below. Each week we'll create a fresh new post to keep the momentum going 🏆 𝗪𝗲𝗲𝗸𝗹𝘆 𝘄𝗶𝗻: Each week we select one member who posted their goals and returned with an update. They receive a community shoutout 🌟 Post your goals today, then return on Saturday or Sunday to share your proof 🔥 Good luck this week!! PS: With the holidays coming up, wishing everyone a Merry Christmas and happy holidays 🎄 Enjoy the time, recharge a bit, and keep the momentum going when you’re back.

I’ve been working through the 7-day Kubernetes guide and hit a small roadblock with Fedora Atomic desktops. The issue is that `dnf install` doesn’t work on these systems, and layering packages with `rpm-ostree` would slow down future updates significantly. # Background: Why I switched to Fedora Atomic Like Mischa, I recently ditched the classic Linux environment for Fedora’s Atomic OS. I was inspired by his approach of treating a personal laptop like production-grade infrastructure. Instead of Silverblue, I went with Fedora Atomic Sway to challenge myself with a tiling window manager and boost my productivity. Now I’m running an immutable OS and learning to containerize everything. Mischa explains the philosophy really well in this video: https://youtu.be/gxWgceGx5Os?si=7cb1LoFmRF3k9mV3 # My solution: Rancher Desktop in Toolbox I wanted to give back to the community, so I figured out how to run Rancher Desktop on Fedora Atomic without using `rpm-ostree` layering (there’s no flatpak available either). The trick is using the toolbox containers that ship with Fedora. I’ve written up the full guide here: https://dev.to/noorlatif/run-rancher-desktop-on-fedora-atomic-desktops-toolbox-container-method-9oi

We’ve all been there — bookmarking useful links, switching devices, and eventually losing track of URLs we meant to come back to. While working on other projects, I realized I was still relying heavily on tutorials whenever things got more complex in Kubernetes. @Mischa van den Burg newsletter last week was the push I needed to step away from guides and actually test whether the theory holds up in a real environment. I decided to deploy Linkding, a self-hosted bookmark manager, on K3s via Rancher Desktop. This helped me move past “Hello World” and understand how production-style applications really behave in Kubernetes: - Self-healing: Watching pods get recreated and replaced - Networking: Seeing how Services expose applications locally - Persistence: Using PVCs so data survives pod restarts - Stateful workloads: Understanding why data needs special handling in K8s By treating this as a real problem to solve, concepts like deployments, volumes, and pod lifecycles finally clicked. If you’re learning Kubernetes, I highly recommend picking one small, real-world tool and deploying it this week. It’s one of the fastest ways to make the theory stick. 📦 Project repo (manifests included):https://github.com/Griffindeetox/linkding-kubernetes