Even the platform engineers need to hide Kubernetes to get their job done:
Kubernetes adds another layer of complexity for platform engineering teams, introducing architectural complexities that require a deep understanding of containers, networking, storage, and cluster security protocols. While it has become the default runtime for modern applications, managing Kubernetes at scale alongside existing VM‑based workloads can overwhelm platform engineering teams. YAML sprawl, cluster life-cycle management, networking dependencies, and security controls consume time that should be spent improving the developer experience and can lead to costly human error.
As a result, many platform engineering teams find themselves serving as infrastructure integrators rather than product engineering teams. They spend cycles wiring systems together, maintaining custom automation, and resolving edge cases between environments. What’s needed is access to solutions that provide an automated infrastructure layer, allowing platform engineers to focus on productizing the platform rather than assembling it.
From “Platform Engineering Needs a Cloud Engine," Taka Uenishi.