User
Write something
Pinned
Start Here: Introduce Yourself & Get Your First Win
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.
Poll
2485 members have voted
Pinned
⚔️ New KubeQuest
Good afternoon Crafters! Last week @Pragalva Sapkota showed exactly what happens when you use KubeQuest the way it’s meant to be used. You can check his post here He set three clear goals, stayed focused, and made more progress in one week than he normally would in a month 🌟 This is the power of direction and consistency. Thanks for the example and commitment, @Pragalva Sapkota . This is the standard we are trying to build here 🙌 ⚔️ 𝗞𝘂𝗯𝗲𝗤𝘂𝗲𝘀𝘁 𝗠𝗼𝗻𝗱𝗮𝘆 𝗶𝘀 𝗹𝗶𝘃𝗲 New week. New chances. 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 and your biggest win Whether you completed every goal or not, accountability 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 we select a member who submitted both their goals and their update. They will receive a shoutout in the community 🌟 Use this week to connect, build, and help others. Post your goals today, then return on Saturday or Sunday to share your proof 🔥 Good luck this week!!
⚔️ New KubeQuest
stay clear of Ozzoy
ozzoy is a YouTube creator whom I had an unfortunate experience thus I saw a chance in posting something useful, a warning to not lose any mony on both his member ship or buying his products. I was encouraged to buy his RHCSA package in order to pass, if you don't ready the description of his products carefully you are and will be fouled 100%, I tried to reach out to him personally and it wan't free. here is my email to him after he refused to guide me one to one arguing that a pdf of 6 files and with little words is enough to have ready to utilize his 50+ gb of files I downloaded. "I am disappointed, I took a. risk buying your products and I lost. I am sad to report to you I will make sure to share my experience so any one with half experience like me don't fall for your expirenced and well tested products wile refusing to help me setting it in order to catch up on my prearatoiin for my test. I am sad and angry. I feel like I got robed, I will keep my YouTube access just so I can salvage what I can. I also feel let down most of all."
stay clear of Ozzoy
The concept of NOT baking environment variables into a Docker image during build time.
I knew about using ARG for build-time variables and relying on a secret manager for runtime envs. But later I realized that even if we use a multi-stage Dockerfile and copy the entire build stage where ARG is used, the image can still end up with baked-in credentials. This is harmful from a security perspective and started worrying me. Then I learned about using --mount in the Dockerfile, which temporarily creates a secret file inside the container and allows passing secrets as an env file during build time, using the same id defined in the Dockerfile. It works. This feature is available with Docker BuildKit. Try it if you were unaware, like me.
0
0
The concept of NOT baking environment variables into a Docker image during build time.
For beginners in Linux...
If you want to learn Linux and you’re just starting out, I’d suggest enrolling in Red Hat’s free subscription. They have a course called “Getting Started with Linux Fundamentals” Try it out and thank me later, the free subscription last for 90 days.
1-30 of 877
KubeCraft (Free)
skool.com/mischa
Only for DevOps Engineers
Get hired to build the future
Use the Community, Blueprint and the KubeCraft Roadmap
Leaderboard (30-day)
Powered by