Common mistakes when using EKS
Finally, let’s round off this chapter by discussing how to configure and manage EKS in an efficient way, applying best practices when possible. Here are some of the common mistakes that we see often when people first begin to use EKS:
- Leaving clusters running: If you don’t need your EKS cluster, shut it down or at least remove or scale in the node groups. Creating a cluster for dev or test environments (or even just to try the code in the book) will cost you real money, so if you’re not using it, shut it down.
- Not having access: The AWS user account used to create the cluster is the only user account that will have access initially. To allow other users, groups, or roles access to the cluster (e.g., using kubectl) you need to add them to the
aws-authConfigMap. Please read Chapter 6, Securing and Accessing Clusters on EKS, for more information. - Running out of Pod IP addresses: With the AWS CNI, every Pod is assigned...
