Say I want to establish a company or an organization's representation on the web quickly. The 'stack' involves domain, email in/out, public-facing website, (optionally) social media presence.

Are there any products out there that unify the 'stack' and allow provisioning from minimal amount of steps? Or do I need to set up each item through separate providers?

Ideal if the solution has an MCP or cli.

Thanks ❤️

i'm working on a decision-making problem where an agent gets a possible leaked api key and has to decide whether it's actually a prod credential and then either ignore, verify or remove/rotate it.

right now i'm using repo context (file path, variable name, surrounding code), key format, git history, whether the code is active/reachable, deployment context, and last_used_at from the provider's admin api.

the problem i'm running into is that most of these signals can tell me "this probably is a real secret", but don't tell me much about whether it's still live or already revoked.

for people who've dealt with secret leaks in actual devops workflows, what do you normally check before deciding what to do with a flagged key?

i'm especially interested in evidence you can get without actually authenticating with the discovered key.

disclosure: this is my own personal project, not a commercial/product promotion. just looking for technical feedback.

Hey everyone,

When I learnt kubernetes and completed CKA, I didn't instantly get a chance to work on a real project. Later, i got a job and learnt a lot, but I felt that there was a need for a tool where we can simulate real world scenarios, we can learn what kind of scenarios and incidents come in real environments.

For this purpose, i built a tool which does exactly the same. You can simulate real world scenarios, use kubernetes tools like opencost, keda, grafana, argocd, traefik. Learn how you can use it and find out different commands to help you learn.

Do check this out if you are interested in this.

I'm curious if other DevOps/platform/SRE teams are running into the same thing my team is.

We're a fairly large environment, mostly EKS, and essentially 100% IaC/Terraform. We also support multiple companies/business units, so while I'd argue our infrastructure is fairly well organized, there's inherently a lot of it and a lot of architecture and context to understand.

Over the last year, our devs have sped up dramatically with AI. The company has leaned heavily into AI-assisted development, reduced developer headcount, and is now pushing toward developers being more "full stack with AI," including having them contribute more of their own infrastructure changes.

In theory, I'm completely in favor of that. I've always wanted developers to be able to own more of the infrastructure surrounding their applications.

In practice, though, it has been kind of a disaster.

We're getting flooded with infrastructure PRs largely written by Claude/other AI tools from developers who don't really understand the infrastructure they're modifying. The Terraform might look plausible, but once you understand the larger system there are frequently significant problems with it.

So instead of reducing the workload on DevOps, it feels like AI has massively increased it.

A huge percentage of our time is now spent reviewing AI-generated Terraform, finding problems, explaining why something won't work, explaining how AWS/EKS/networking/IAM/CI/CD/etc. fit together in our environment, and then going through another iteration of an AI-generated PR.

There's an interesting asymmetry I've noticed too. Our DevOps team is mostly made up of former software developers who moved toward infrastructure, automation, and pipelines. Most of us can jump into application code and be productive pretty quickly, especially with AI helping us. Like,...I feel like (and have some evidence to support) that our small DevOps team could largely take over all of the dev's tasks, but they are falling on their faces trying to deal with ours.

AI seems extremely good at helping someone who understands software write more software. It seems much less capable of allowing someone without infrastructure experience to suddenly understand a large production environment.

The complaint we're increasingly hearing is basically: "We can't successfully do full-stack development with AI because the infrastructure is too complicated."

And maybe they're right, but before AI, I would have said that this company is the most organized and best architected I've ever been at. I mean....100% IaC has never been something I've experienced, and it's very rare that we hit a use case brought up by one of the several companies where we don't already have a set of generalized modules that can't support it.

Our environment is complex, but a lot of that complexity isn't accidental. We have a large organization, multiple companies we deploy for, Kubernetes, networking, security requirements, IAM, CI/CD, observability, etc. You can't abstract away the fact that these things exist. And we're already 100% Terraform/IaC, which I would have thought would make this considerably easier for AI to reason about than an environment full of manually configured infrastructure.

The strangest part is the staffing effect.

AI allowed the organization to reduce software engineering headcount because individual developers became more productive. But now those remaining developers can generate changes so quickly that our DevOps team is completely overwhelmed trying to support and review them.

It genuinely feels like we could double the size of the DevOps team right now and still have plenty of work. We are working on an AI assistant that can help the devs deploy to our environment more effectively, but we're having a hard time finding time to work on it because we're constantly helping the devs.

I'm starting to wonder whether this is going to be a broader consequence of AI-assisted development: AI increases the rate at which software can be produced much faster than it increases the rate at which infrastructure/platform teams can safely absorb changes.

For those of you working in DevOps/platform/SRE at companies heavily adopting AI:

Are you seeing this too?

And if you are, how are you handling it?

Have you increased platform/DevOps staffing? Built better abstractions or internal developer platforms? Given developers more direct infrastructure ownership? Put stricter boundaries around what application teams can modify? Found ways of giving AI enough context about your infrastructure that it actually produces good changes?

Or has AI actually reduced your infrastructure workload, and we're doing something wrong?

I recently completed the full Kubestronaut certification path after roughly three months of focused preparation.

After completing it, quite a few people reached out asking about the order I followed, the resources I used, and how I prepared for each exam, so I decided to put everything together in one detailed blog rather than answering the same questions separately.

For KCNA and KCSA, my preparation was fairly straightforward and mainly consisted of the KodeKloud courses, KodeKloud notes, and practice tests, while CKAD, CKA, and especially CKS required much more hands-on practice with labs, mock exams, and repeated work on weaker areas.

I’ve also included links to my dedicated CKAD, CKA, and CKS exam-experience posts for anyone who wants a deeper breakdown of those exams.

Full 3-month Kubestronaut journey:
https://medium.com/@prateekjain.dev/my-3-month-journey-to-becoming-a-kubestronaut-c722c4a7cf75?sk=eb78b3ef703262f787f746cc6969d8f1

Hopefully this helps anyone currently working towards the Kubestronaut path. Happy to answer questions about the preparation or any of the five exams.

I have someone pushing a colleague to an Openshift virtualization position. We do multi cloud deployments, GHA heavily, ephemeral integration environments, etc. Not seeing the intersection with this guys skills or desires. Am I missing something?

After I first set up a deployment pipeline, I would simply drop DB passwords and API keys into GitHub Secrets and feel completely safe because they are encrypted. I recently went through a security breakdown on GitHub Actions that showed me that it could be a mistake to think that way.

The main issue is that an encrypted secret is still a static, long-lived target. Once the workflow finishes, that credential stays active indefinitely. In the breakdown, I saw a few default behaviors attackers look for, like teams forgetting to revoke access after a job runs or lacking the audit logs to even know when a key was used.

The proposed fix is shifting to dynamic orchestration where the pipeline generates a short-lived token at runtime and revokes it the second the deployment finishes.

If you're writing deployment workflows, how do you handle this, do you just use GitHub's default storage, or are you injecting temporarily credentials to avoid leaving static keys exposed?

I recently set up a small 3-node Kubernetes homelab using Dell OptiPlex Micro PCs running Talos Linux.

The main goal was to have a local cluster where I can learn, experiment, break things, and test tools without relying on cloud infrastructure every time. I’m planning to use it for Kubernetes networking, storage, observability, GitOps, security, upgrades, and general experimentation.

Small setup, but already a very useful playground.

Curious what others here are running for their Kubernetes homelabs.