Amazon EKS Operations

Internal

• Amazon Elastic Kubernetes Service
• aws-iam-authenticator
• kubectl
• eksctl

Cluster Information

Cluster Status

aws eks [--region us-east-1] describe-cluster --name example-cluster --query "cluster.status"

"ACTIVE"

If the right region is configured in the profile, there is no need to be specified.

Cluster Endpoint

aws eks [--region us-east-1] describe-cluster --name example-cluster --query "cluster.endpoint" --output text

https://FDXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX.gr0.us-east-1.eks.amazonaws.com

If the right region is configured in the profile, there is no need to be specified.

Cluster Certificate Authority

aws eks [--region us-east-1] describe-cluster --name example-cluster --query "cluster.certificateAuthority.data" --output text

LS0t...LQo=

If the right region is configured in the profile, there is no need to be specified.

Connect to an EKS Cluster with kubectl

https://docs.aws.amazon.com/eks/latest/userguide/getting-started-eksctl.html

Update .kube/config with the EKS cluster definition as follows:

aws eks [--region us-east-1] update-kubeconfig --name example-eks-cluster [--alias <context-alias>]

If the right region is configured in the profile, there is no need to be specified.

If no alias is used, the default is the cluster ARN.

The result is to add a new context to .kube/config:

Added new context arn:aws:eks:us-east-1:999999999999:cluster/example-eks-cluster to /Users/testuser/.kube/config

The default name of the context is the name of the IAM role, but it can be changed to make it more wieldy.

Load Balancer Troubleshooting

https://aws.amazon.com/premiumsupport/knowledge-center/eks-load-balancers-troubleshooting/