Docker Hardened Images used to be locked behind Docker Business and Enterprise plans, typically costing teams $200–300 per developer per year. Now they are open source and available to everyone. This matters because most container CVEs come from base images, not application code. Teams paid to reduce that noise or accepted the risk. By removing the paywall, Docker is pushing secure base images from “enterprise upgrade” to baseline. https://www.docker.com/products/hardened-images/

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

Good afternoon Crafters! As we’re closing 2025, this is what finishing strong looks like. Last week @Adeyemi Ojo executed KubeQuest exactly as intended. Three goals set. Three goals completed. Proof delivered. He moved from testing things to running a real setup. That’s exactly how KubeQuest is meant to be used. Nice work @Adeyemi Ojo and thanks for setting the example 🙌 ⚔️ 𝗞𝘂𝗯𝗲𝗤𝘂𝗲𝘀𝘁 𝗠𝗼𝗻𝗱𝗮𝘆 𝗶𝘀 𝗹𝗶𝘃𝗲 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: Use this week to build and learn. Reach out to someone in the comments and show some support.

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

Hi, I have been procastinating this journey, rising and falling and just stumbled on kubecraft DevOps goal setting. I have got myself an old laptop ready to break and fix and learn with it. I have gotten myself comfortable with the Linux terminal. One milestone I will like to achieve is installing Arch. I have attempted doing this three times now and have failed. My goal for this week is to install Arch. I have also started learning file systems and will love to install Arch, break it and install it again