Introducing Kubernetes Resource Orchestrator (KRO)

Providing application teams with a self-service way to deploy applications and their dependencies often means platform administrators must hide platform implementation details behind simple-to-consume APIs. In Kubernetes, this usually means deploying custom resource definitions that are either third-party or built in house. These CRDs not only allow users to manage non-Kubernetes objects through the Kubernetes resource model, but also abstract how some resources are created and managed.

In this session, attendees will 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 Kubernetes workflows for better scalability and simplicity