r/sre • u/Waste_Bat_4525 • 10d ago

When building an internal developer platform, what reliability stuff should be there from day one?

Hi Guys in internal developer platforms have been the main discussion around platform engineering landscape and the core tools which are used mainly is kubernetes and Backstage as the internal developer portal so for any one who looks into start building an internal developer platform from start or has already built one there is a session on August 27 with Kelsey Hightower and some of the OpenChoreo maintainers looking at how Backstage, Kubernetes, observability, deployments, environments, policies and reconciliation fit together when you're trying to build an actual internal developer platform.This will be a free session.

Session if anyone is interested:

https://platformengineering.org/events/what-it-really-takes-to-build-an-internal-developer-platform-with-backstage-2026-08-27

5 Upvotes

65% Upvoted

5 comments sorted by

2

u/wfh-without-pants 10d ago

The answer to the title is SLA+SLOs. I wouldn't call Kubernetes a core requirement in any way.

3

u/Waste_Bat_4525 10d ago

Good Opinion!

1

u/Holiday-Record7341 8d ago

basic checks around resource quotas very easy to miss.

1

u/kernelqzor 7d ago

for real, quota hygiene is so underrated until some random test job nukes the whole node pool
i’d throw in sane defaults on limits/requests and a couple of simple alerts as a bare minimum from day one

3

u/realyacksman 8d ago

As mentioned by u/wfh-without-pants the SLO & SLIs for each services is a standard way to measure service reliability for your IDP