Original: Developers and platform teams both want Kubernetes self-service. They disagree on who owns it. – Chris J. Preimesberger. Summarized by AI on September 25, 2026.
While both developers and platform teams desire Kubernetes self-service, they fundamentally disagree on operational boundaries. Giving developers direct access to raw Kubernetes APIs merely shifts the burden of debugging manifests and storage drivers away from writing code, while operations teams face overprovisioning and unreviewed configurations.
The practical resolution is a paved path where platform teams define the security, networking, and lifecycle guardrails, and developers choose from a supporting menu of approved configurations. This division of responsibility compresses provisioning workflows from weeks to minutes by automating the underlying infrastructure while preserving necessary governance.
Ultimately, successful self-service does not hide Kubernetes but standardizes the enterprise processes surrounding it.
Coté: the Kubernetes people kept trying to tell us thet Kubernetes is not for developers and they should not be exposed to it. But, here we are, still.
Links
🤖 Developers and platform teams both want Kubernetes self-service. They disagree on who owns it. – A look at the friction between developers and platform teams over Kubernetes self-service, proposing a paved path that balances developer autonomy with strict operational guardrails.
Leave a Reply