Which solution will meet these requirements with the LEAST operational overhead?
Use Amazon CloudWatch Container Insights to collect and group the cluster information.
Use Amazon EKS Connector to register and connect all Kubernetes clusters.
Use AWS Systems Manager to collect and view the cluster information.
Use Amazon EKS Anywhere as the primary cluster to view the other clusters with native Kubernetes commands.
Explanations:
Amazon CloudWatch Container Insights is primarily used for monitoring and logging containerized applications but does not provide a central view of both EKS and on-premises clusters. It focuses on performance and operational metrics rather than centralized cluster management.
Amazon EKS Connector enables users to register both Amazon EKS and on-premises Kubernetes clusters with a central management interface. This allows visibility into all clusters and workloads from a single location, making it the most efficient and low-overhead solution for the company’s needs.
AWS Systems Manager is primarily designed for managing AWS resources, including EC2 instances and other AWS services. While it has capabilities to manage and monitor resources, it is not specifically tailored for centralized Kubernetes cluster management across different environments like EKS and on-premises clusters.
Amazon EKS Anywhere allows users to run EKS on their own hardware, but it does not inherently provide centralized visibility into multiple clusters, especially across different environments. Using it as a primary cluster may add complexity rather than reduce operational overhead.
I organize that the answer is:
Use Amazon EKS Connector to register and connect all Kubernetes clusters.