DevOps Blog

Devops.dev is a community of DevOps enthusiasts sharing insight, stories, and the latest development in the field. Press enter or click to view image in full size What building DotShare AI 3.5.2 taught me about release boundaries, evidence, and credential handling. A deployment can be correct while the explanation of that deployment is wrong. The artifact comes from a specific commit. The announcement comes from someone’s editor, a few recent commits, and an AI draft.

You probably don’t have a scaling problem. You have a boundaries problem, and there’s a cheaper way to fix it. Press enter or click to view image in full size One deployable, strict boundaries, and a clean exit path. Most teams that go microservices early aren’t reacting to load. They’re reacting to a codebase where everything calls everything, and they hope a network will force some discipline. It does.

Devops.dev is a community of DevOps enthusiasts sharing insight, stories, and the latest development in the field. Press enter or click to view image in full size Many DevOps engineers can run: 🐳 Docker ☸️ Kubernetes πŸ”„ CI/CD pipelines ☁️ AWS πŸ—οΈ Terraform 🌐 Networking tools And everything feels comfortable. Until the interviewer asks: β€œWhat actually happens internally?” Suddenly, knowing the command isn’t enough.

Devops.dev is a community of DevOps enthusiasts sharing insight, stories, and the latest development in the field. Recently, a friend attended a Coforge DevOps Engineer interview, and the questions were heavily focused on practical engineering scenarios.

The architecture, the egress-only operator, Entra ID and RBAC, networking, and Private Link, plus the setup traps and preview gaps to check before production Press enter or click to view image in full size Anyscale on Azure runs managed Ray on your own AKS cluster, and its security model comes down to one design choice: the Anyscale control plane never connects to your cluster.

100 Days of DevOps Your Kubernetes Pod is running. The deployment looks healthy. Everything seems fine. But can anyone actually access your application? This is where Kubernetes stops being a collection of YAML files and starts becoming a lesson in real infrastructure engineering. A running container doesn’t automatically mean a working application. You need a way to organize workloads, manage resources, expose services, and handle storage.

Press enter or click to view image in full size Source: Author Not a medium member? Read here! Early morning, the phone rings and is THAT notification… One of the shards of the database is hanging: locks is growing, timeouts increasing, and the application team is already in the call. So you joined and the assumptions start: Throttle traffic? Could it be an attack? Is it the network? Every hypothesis is reasonable, and every one requires an investigation and an explanation of why not.

Devops.dev is a community of DevOps enthusiasts sharing insight, stories, and the latest development in the field. Press enter or click to view image in full size VectorStep’s tag line I’ve spent most of my career in observability, in industries -banking, insurance, healthcare - where “let the AI just handle it” isn’t a casual decision. VectorStep, the AI pipeline orchestration tool I built out of that experience, went public this week.

Hybrid post-quantum TLS already ships in every major browser. Your servers are the part that’s lagging — here’s how to check them in five minutes. Press enter or click to view image in full size Image created with the help of AI Most teams file post-quantum cryptography under “later.” That’s the wrong drawer. The attack doesn’t need a quantum computer today.

Company: Wipro Role: DevOps Engineer Experience: 5–8 Years Interview Mode: Virtual Interview Date: 10-Sep-2026 Press enter or click to view image in full size For a 5–8 year DevOps interview, knowing commands isn’t enough. The interviewer wants to know whether you understand what is happening, where it is used, how you troubleshoot it, and how you would handle it in production.