Recent advancements in cloud services, particularly Amazon's new EKS capabilities, indicate a shift towards managed GitOps and resource management tools. The Kube Resource Orchestrator (kro) is emerging as a key player in this space. It aims to simplify how Kubernetes resources are grouped and managed, showcasing the industry's growing interest in enhancing platform engineering workflows. As platforms increasingly rely on declarative Infrastructure as Code (IaC) tools, the number of Custom Resource Definitions (CRDs) can explode. Projects like Crossplane and AWS Controller for Kubernetes can introduce hundreds or thousands of new CRDs, making effective resource management essential for platform teams. Kro's main feature is the ResourceGraphDefinition, which abstracts multiple Kubernetes objects into a single API. This API allows users to configure resource requests, manage dependencies, and track statuses more straightforwardly. By providing a clear composition framework, kro reduces the need for complex tools like Helm or Kustomize. However, challenges remain for users. They often find themselves needing to fill gaps in their platform designs, similar to the “How to draw an owl” meme, where kro provides basic shapes but requires significant effort to complete the overall picture. Successful platforms focus on three main outcomes: reducing time to deliver new services, patch existing services, and introduce new capabilities. Platforms that excel in these areas empower users to push new ideas into production quickly and reduce dependencies on central teams. They rely on principles like composition, encapsulation of various processes, and decoupled delivery across environments. While kro excels in composition, it doesn't address workflow management or integration with external systems. Other frameworks, such as Kratix, complement kro by handling these broader orchestration needs. The growing community around kro is a positive sign for its future. As more organizations look to integrate kro into their architectures, understanding its role in composition versus orchestration is crucial. Kro provides a powerful tool for resource management, but it needs to be tied to broader capabilities that encompass configuration, policy, and deployment across different environments to maximize its value.