Managing Kubernetes clusters can be a daunting task, especially as organizations scale their use of Kubernetes. The process often involves creating clusters, adding organization-specific components, and ongoing management, which can lead to complications and errors. Traditionally, this requires juggling multiple Infrastructure as Code (IaC) tools, Kubernetes manifests, and Helm charts. This article highlights a solution using Amazon Elastic Kubernetes Service (EKS), Kube Resource Orchestrator (kro), and AWS Controllers for Kubernetes (ACK) to streamline cluster management. ACK allows users to manage AWS resources through Kubernetes using declarative YAML constructs. This means that once an ACK service controller is installed, users can create Custom Resources (CRs) to generate AWS resources necessary for EKS clusters. The article emphasizes the challenges of managing dependencies between these resources, such as the order in which they must be created. For example, a Virtual Private Cloud (VPC) must exist before subnets can be created, and IAM roles need to be set up prior to creating an EKS cluster. To manage these dependencies effectively, kro acts as an abstraction layer that ensures resources are created in the correct order and linked appropriately. Kro’s ResourceGraphDefinition (RGD) facilitates this process by grouping all necessary AWS and Kubernetes resources into a single unit. Users can define RGDs for scenarios like creating an EKS cluster with or without a pre-existing VPC. By using Common Expression Language (CEL), the system can extract values from one CR and pass them to another, ensuring resources are created in the right sequence. This method simplifies the orchestration of resources and reduces the risk of errors. The article also touches on creating cross-account AWS resources, aligning with AWS's recommendation for a multi-account strategy to enhance isolation and management of applications. This approach provides a more organized framework for managing Kubernetes clusters within AWS, allowing for better productivity, consistency, and reduced operational overhead.