[thinkingkong]

Having built a bunch of these, the article more or less skips past the hard stuff. When you build an internal PaaS you aren't building the k8s part, you're building and prescribing the entire developer workflow to the team. If you do it well then it makes self-service super easy but the opinions on how to do everything are baked in. For example, you get opinionated versions of a build pipeline, SPA hosting, deployment models, yaml templating (or some other config language), dependency trees, monitoring and alerting systems, identity, secrets management, etc. All of those things end up being baked into the system if it's going to be successful. It's a tall order and I'd love to read more about internal PaaS failures than successes; thats where the learning is going to be.

[thiry]

I agree that the main challenge is to get the developer workflows right and being prescrptive here often should not be a problem from the developers' perspective.

And yes, it would be great to generally hear more about failures but naturally people are less willing to share these stories, I guess.