For administrators
Troubleshooting
8 min
introduction in this section you can find some of the common issues you might encounter and ways you can try to solve them expired mfa token an error occurred (expiredtokenexception) when calling the describecluster operation the security token included in the request is expired if you are getting this error your mfa token has expired and you need to run hosty auth command this has to be done every 24 hours outdated kubectl config couldn't get current server api group list get " http //localhost 8080/api?timeout=32s http //localhost 8080/api?timeout=32s " dial tcp \[ 1] 8080 connect connection refused execute aws eks update kubeconfig name=\<clustername> to update kube config pods stuck terminating if you try do delete the eks cluster and get error context deadline exceeded and the last operation before this error was something like module cluster dragon kubernetes namespace v1 production\["website"] still destroying \[id=website production, 4m50s elapsed] most likely one of the pods got stuck terminating you can check that by running kubectl get pods n \<namespace> you should see something like name ready status restarts age website production drupal 8454559f74 tfk5d 0/2 terminating 0 39h you can get it unstuck by force removing stuck pods by running kubectl delete pods all grace period=0 force=true n \<namespace> for example kubectl delete pods all grace period=0 force=true n website production environments are successfully deployed, but not accessible via url most likely culprit is service responsible for mapping target groups with alb rules to check its logs, do kubectl get pods kubectl get pods n kube system get logs for logs for the pod kubectl logs n kube system aws load balancer controller \<rest of the pod name> you might see an error like ,"error" " toomanyuniquetargetgroupsperloadbalancer you have reached the maximum number of unique target groups that you can associate with a load balancer of type 'application' \[100]\n\tstatus code 400, request id or some other error this particular limit is caused by too many development environments solution is to remove the unused environments and redeploy the problematic environments