Developers and platform teams both want Kubernetes self-service. They disagree on who owns it.

Kubernetes self-service creates friction between developers wanting fast environment access and platform teams responsible for cost, access, and policy compliance. HPE product managers Marius Bogoevici and Karthik Subramanian argue the answer is a 'paved path': developers get approved, catalog-based choices (cluster versions, resource quotas, toolsets, lease durations) while platform teams retain control over networking, identity, security policy, and lifecycle governance. The piece describes how HPE's HKS Kubernetes distribution paired with HPE Morpheus Software implements this division of responsibility, compressing provisioning from weeks to hours through service catalogs, RBAC, and automated lifecycle controls, while cautioning that security and governance must be designed into the self-service layer from the start rather than bolted on afterward.

Source: https://thenewstack.io/kubernetes-self-service-platform-teams. 8 Sync News only summarizes and links out; content copyright belongs to the authors and original sources.