To empower application teams with self-service deployments, platform administrators must hide underlying complexity behind simple, consumable APIs. In the Kubernetes ecosystem, this usually requires building or maintaining Custom Resource Definitions (CRDs). While CRDs allow users to manage both cloud and local resources via YAML, they are often difficult to build and maintain at scale.

Kubernetes Resource Orchestrator (KRO) changes this dynamic. Instead of writing complex controllers from scratch, KRO allows platform teams to easily bundle multiple resources into a single, high-level API.

In this session, you’ll learn how KRO helps you:

- Reduce YAML Fatigue: Create high-level APIs that hide boilerplate while keeping the flexibility developers need.
- Unified Orchestration: Seamlessly manage both native Kubernetes objects and cloud-specific resources (like buckets, topics and IAM) in one place.
- Scale Efficiently: Integrate KRO into existing workflows to simplify platform management and improve developer experience.