r/platformengineering • • 13h ago

how do you decide when a team really needs an internal developer portal

6 Upvotes

we keep seeing teams jump to backstage or something similar as soon as there are 10 services. my gut says it only pays off once people actually waste time hunting for owners, docs and runbooks, and before that a good readme template and a simple service list does most of the job. where is the line for you, number of teams, number of services, or just the pain of onboarding?


r/platformengineering • • 31m ago

I built a game to learn kubernetes - Night Shift

Thumbnail
play.snowops.net
1 Upvotes

I have been working on multiple projects and one thing I felt was the biggest challenge for adoption. Setup time. If something takes up more than 5 minutes, you lose 90% of your potential users.

For this, i created a browser game which helps you learn real world kubernetes incidents within your browser. It's free and no setup required.

All the results are from logs of my another project - Snowops Labs. So, everything you will get is real.

It teaches you how the real engineering team works and gives you real incidents to solve and learn.

I'd genuinely like to hear what experienced engineers think. Especially if you've spent time troubleshooting production incidents.

TL;DR: An attempt to make practical DevOps troubleshooting more interactive and game-like. Give it a try and tell me what you think.


r/platformengineering • • 1h ago

Shutting down the whole platform to stop an attacker: what we revoked, rebuilt and brought back first (Bitrise incident review, with IOCs)

Thumbnail
bitrise.io
1 Upvotes

r/platformengineering • • 7h ago

Who owns policy orchestration once you have dozens of accounts?

1 Upvotes

Writing a guardrail is the easy part. Rolling it out across lots of accounts and OUs, with exceptions, without breaking someone’s deploy on a Friday, seems to be the actual job. That policy orchestration piece is what I’m curious about.

How do you handle it? Guardrails in Terraform with a PR review from security? A dedicated platform team? Rollout to a test OU first, then wider? And where do exceptions live so they don’t turn into permanent holes?

Blast’s angle is compiling security principles into native cloud guardrails and testing the business impact. Act Security tends to start from which access each workload actually uses and builds the policies from there. Should be upfront that Act is one of the companies my agency works with.

Mostly interested in the people and process side. Who gets paged when a guardrail blocks prod?


r/platformengineering • • 7h ago

who gets the vuln ticket when the app and base image have different owners?

1 Upvotes

say platform owns the base image, the app team has to rebuild and deploy it, and CODEOWNERS still points at the team that had the repo before the reorg. so the ticket bounces.

for people routing findings with Nucleus, Rival, or homegrown rules, who gets the first ticket? the team that can patch the image or the one that can get the fix into prod?


r/platformengineering • • 9h ago

Canary analysis on a thin metrics budget, worth it or just put tracing back?

1 Upvotes

We moved our Spring Boot services off New Relic to self-hosted Prometheus and Grafana and dropped most custom tracing. Then a release went out, rollout status green, 5xx flat, but one code path was failing inside a try/catch and returning a fallback. Rollback was easy. Finding the commit took a day.

Team’s split. Half want OpenTelemetry tracing back. Half want a canary step. Flagger and Spinnaker’s Kayenta both read the metrics we already have, and the one we needed didn’t exist. Hud counts calls and exceptions for every function, caught ones included, so nobody has to define the metric first.

Anyone pick rollout verification over rebuilding tracing and not regret it?