A SysOps administrator deployed an Amazon EKS cluster that runs pods on AWS Fargate. The cluster is up and running. To manage the cluster using kubectl from the administrator’s workstation, what must be configured locally so kubectl can reach the cluster API?

To manage an Amazon EKS cluster using kubectl from a local workstation, a kubeconfig file is essential. This file contains the necessary cluster details (API server endpoint, certificate authority data) and user authentication information (credentials) that kubectl uses to connect securely to the EKS cluster's API server. AWS provides commands, like aws eks update-kubeconfig, to automatically generate and configure this file for your cluster. Incorrect options: The kube-proxy add-on runs within the EKS cluster to maintain network rules and facilitate service discovery, it is not installed locally on the administrator's workstation. A Fargate profile defines which pods run on Fargate within the EKS cluster; it is configured within EKS, not on the local machine. An eks-connector.yaml file is used for EKS Connector, which allows you to connect any conformant Kubernetes cluster to EKS for management, not for basic kubectl access to an EKS cluster itself.