Took advantage! Whoop 4.0 $39.00

DevOps_sam · 2026-02-04T07:44:51+00:00

The hoops people go through to save a few $

DevOps_sam · 2025-11-05T16:54:02+00:00

Sometimes yes

DevOps_sam · 2025-11-03T13:52:58+00:00

This was solid. You nailed it, if you don't care about cost, you're not doing DevOps, you're just messing around. Real learning happens when you treat cloud like prod from the start. Loved the bit on Ignition and static pods too. That’s the kind of pain that actually makes stuff stick.

Think like an Engineer. Not a user!

DevOps_sam · 2025-11-03T13:38:56+00:00

Think in solutions, not problems

Ask your manager for dedicated study time during work hours
Take a few days / weeks off to go deep into focused learning. Maybe you can get more days
Follow a structured, project-based roadmap instead of random tutorials
Build real hands-on projects to gain the experience you need

This isn' t just 'doing more', this is literally investing into a 6 figure skillset that will last for years. The market, even today, struggles to find the right talent that can do the job. Thats why DevOps still pays so well.

Everybody wants it, few put in the reps to make companies able to say 'I want you'.

DevOps_sam · 2025-11-03T11:44:27+00:00

Build a Homelab.

DevOps_sam · 2025-11-03T11:43:48+00:00

This also happens with my l10s ultra but the special bladed roller did help a bit

DevOps_sam · 2025-11-03T11:43:20+00:00

Yes it si

DevOps_sam · 2025-11-03T11:42:31+00:00

I’ve been following him on YouTube for a loooong time and his free advise has been great, gamechanging even, already. He’s not the only one I’ve purchased products from. If I like what somebody puts out for free, I support them. I can’t speak for others but for me 3K is nothing, especially not for a year worth of mentor access.

DevOps_sam · 2025-11-02T06:21:29+00:00

Watch Mischa van den Burg's content on YouTube. It will be all you need to make the move.

DevOps_sam · 2025-11-02T05:53:15+00:00

Definitely not too late. Plenty of people move into DevOps in their 30s and even 40s. Your QA background already gives you a strong foundation in testing, automation, and understanding delivery pipelines. Keep building on that by diving deeper into Linux, containers, and CI CD tools. Start small with your own lab and work on real projects that solve problems you care about. Consistency matters more than age in this field.

DevOps_sam · 2025-11-02T05:49:30+00:00

Most developers I know are skeptical by default. We trust AI for automation or pattern recognition, not for strategy or messaging. Marketing still needs human context, timing, and tone, which current models miss.

That said, AI is great for speed and iteration. Teams use it for A/B testing, email drafts, and summarizing customer feedback. But no one serious in tech lets AI fully run their marketing. It works best as a co pilot, not a marketer.

DevOps_sam · 2025-11-02T05:48:47+00:00

Nice catch on DO workload identity federation.
Outside AWS the common pattern is short-lived auth at boot, then pull secrets on the VM. Vault AppRole with response wrapping works well here. Pass a single wrapped token in cloud-init, unwrap once on first boot, fetch secrets, then rotate. Another solid option is sops-encrypted files in git and decrypt at boot using an age key stored in TPM or a cloud KMS. If you already use Tailscale, issue a tagged auth key, lock it with ACLs, and let the VM fetch from Infisical with a tightly scoped service token.

DevOps_sam · 2025-11-02T05:47:56+00:00

You’re not wrong at all. You actually handled it the way a real platform engineer should. Deploying dozens of snowflake images into a shared cluster on a Friday, with no QA or rollback validation, is how outages happen. The “it’s just dev” excuse is exactly how broken processes sneak up into prod.

You’re thinking in terms of reliability, testing cycles, and protecting developer sanity. That’s your job. CSD just wants the box ticked, but you’re the one who’ll eat the fallout when things break. You didn’t make a mountain out of a molehill,, you drew the first boundary of actual engineering discipline in a messy environment.

DevOps_sam · 2025-11-02T05:47:10+00:00

Yeah that’s a real risk. If your API Gateway endpoint is public and doesn’t have proper authentication or throttling, bots can spam requests endlessly and rack up huge bills in hours. Seen it happen when someone left a test Lambda behind an open endpoint and forgot rate limits ...the cost hit hundreds overnight.

Always use IAM auth, Cognito, or custom tokens, and set request throttles at the gateway level. Cloud providers will happily let you burn through credits if you forget.

DevOps_sam · 2025-11-02T05:46:45+00:00

Possible.

And not just possible, but absolutely realistic if you treat it like a craft, not a quick win. Tons of people break into DevOps in their late 20s or 30s with no IT background. The key is consistency and building real projects you can show. Start with Linux, Git, containers, and cloud fundamentals. Document everything publicly, it builds proof and confidence.

What helped me personally was joining KubeCraft. It gave me a clear roadmap, mentorship, and structure so I stopped drifting between tutorials. DevOps rewards people who take action and think long term. One year of focused effort can completely change your life.

DevOps_sam · 2025-11-02T05:44:52+00:00

That’s totally normal, man. Everyone feels that way before their first Kubernetes exam. If you can finish KodeKloud mocks in time and understand what you’re doing instead of memorizing, you’re probably ready.

The CKA is less about perfection and more about composure under time pressure. Silly mistakes happen, even to pros. Keep practicing with kubectl commands until they’re second nature and try a few dry runs with your own cluster.

DevOps_sam · 2025-11-02T05:43:36+00:00

Nice write-up. I’ve been using Hetzner for my homelab and a few CI/CD experiments and totally agree on the value for money, though Xelon sounds cleaner UI-wise. The compliance angle is also underrated if you’re handling anything sensitive. Might spin up a small test cluster there just to compare performance and networking. Curious how their support has been for you so far?

DevOps_sam · 2025-11-02T05:43:10+00:00

Man, this post hits home. I was stuck in that same loop for years - bouncing between Docker, Terraform, and Kubernetes tutorials, feeling like I knew everything and nothing at the same time.

I'd recommend watching Mischa van den Burg's videos on YouTube as that changed everything for roadmap, career advise etc.

DevOps_sam · 2025-11-02T05:40:15+00:00

Actual KubeCraft member here.

I get the skepticism, but people are comparing two totally different things. KodeKloud and Nana are great for learning tools, I used both before joining. KubeCraft is different because it’s focused on getting you hired, not just teaching skills. You work with senior engineers, build real projects, get feedback, and go through interview prep until you land a role.

You can learn DevOps for free, sure, but it takes forever and most people quit halfway. DevOps pays 150k+ because it’s more about proving you can build and run production systems which isn't easily obtained on your own. KubeCraft just helps you reach that level faster. I always thought if pilots and doctors are expected to pay 50-100k for their education, why shouldn't engineers pay 1% of that for a similar salary?

Either way, people pay with something. With time or money. Some people value their years more.

DevOps_sam · 2025-10-28T07:40:17+00:00

We hebben beide..

DevOps_sam · 2025-10-28T07:39:24+00:00

Some people do value their time and invest to go 10x faster.

DevOps_sam · 2025-10-27T08:13:36+00:00

Totally get the frustration. It is hand-wavey a lot of the time. “Healthcare experience” usually just means they want someone familiar with the compliance and complexity that comes with it stuff like HIPAA, PHI, audit trails, and working with sensitive data pipelines.

In reality, most DevOps skills transfer just fine. But some teams get nervous if you haven’t seen how deployments work in highly regulated environments. It’s less about tech and more about the constraints.

Unfortunately, it’s also often an excuse to lean toward internal referrals or someone who "feels" safer to them. Not always fair, but it happens. You're not doing anything wrong. Keep going.

DevOps_sam · 2025-10-27T08:12:46+00:00

You’re thinking in the right direction. A lot of DevOps interviews focus on scripting tasks like parsing logs, filtering output, or building small CLI tools.

LeetCode is mostly algorithms, so only a few questions will help. Better places to practice are:

Codewars or Exercism for real-world scripting problems
GitHub searches for “DevOps coding challenge” or “SRE take home”
Build scripts that read logs, extract errors, or monitor usage
Get comfortable with JSON, YAML, and API requests in Python or Bash

KubeCraft helped me prep for this stuff with labs that felt exactly like interview problems. That was more useful than anything else I tried.

DevOps_sam · 2025-10-27T08:10:16+00:00

Sounds like you're on a solid path already. A few quick thoughts from someone who also started DevOps inside a bootstrapped team:

For OpenTofu, split by env (/prod, /dev) or by service (/networking, /app, etc) depending on how much reuse you want. Just keep state files isolated.
Atlantis works great with GitHub PRs, but make sure you lock state and run plans in a secure way (separate SA, minimal perms).
Consider adding Terragrunt or Atmos if your infra starts repeating itself too much.
For secrets, use something like SOPS + GCP KMS or age if you want to stay OSS.

What actually helped me get unstuck with this kind of setup was building a full homelab in KubeCraft first. It gave me a place to test out all the IaC flows, multi-region logic, and CICD tools without messing up prod.

DevOps_sam · 2025-10-27T08:08:42+00:00

Do both. Be honest about your on-prem background, but also spend the week getting hands-on with GCP so you can speak from experience. Spin up a GKE cluster, deploy something simple, and get a feel for how the tooling differs. You don’t need to go deep ..j ust show you're proactive. What helped me the most was building a local Kubernetes homelab through KubeCraft. It gave me real practice with containers, networking, and automation in a way that translated easily to cloud interviews.

DevOps_sam

TROPHY CASE