Amazon EKS Operations: Difference between revisions
Jump to navigation
Jump to search
| Line 12: | Line 12: | ||
==Cluster Status== | ==Cluster Status== | ||
<syntaxhighlight lang='bash'> | <syntaxhighlight lang='bash'> | ||
aws eks --region us-east-1 describe-cluster --name example-cluster --query "cluster.status" | aws eks [--region us-east-1] describe-cluster --name example-cluster --query "cluster.status" | ||
"ACTIVE" | "ACTIVE" | ||
</syntaxhighlight> | </syntaxhighlight> | ||
If the right region is configured in the profile, there is no need to be specified. | |||
==Cluster Endpoint== | ==Cluster Endpoint== | ||
Revision as of 00:29, 8 August 2020
External
Internal
Overview
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
Cluster Certificate Authority
aws eks --region us-east-1 describe-cluster --name example-cluster --query "cluster.certificateAuthority.data" --output text
LS0t...LQo=
Connect to an EKS Cluster with kubectl
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 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.