Providing application teams with a self-service way of deploying applications and their dependencies often means that platform administrators have to hide the implementation details of the platform via simple to consume APIs. In the case of Kubernetes this usually means having to deploy Custom Resource Definition that are either 3rd party or custom built in-house. These CRD’s in addition to allowing Kubernetes users to manage non-Kubernetes objects via the Kubernetes Resources Model (Aka YAML file), they also allow abstracting away the details of how some resources get created and managed.

In this session, you'll learn how KRO allows platform teams to:
- Create high-level APIs that reduce YAML complexity while maintaining flexibility
- Support both native Kubernetes and cloud-specific resources for more efficient orchestration
- Integrate KRO into your Kubernetes workflows for better scalability and simplicity