Your Browser is Out of Date

Nytro.ai uses technology that works best in other browsers.
For a full experience use one of the browsers below
Amazon Elastic Kubernetes Service Anywhere Bare Metal on Dell PowerFlex
Introduction PowerFlex product overview Solution architecture Installing an Amazon EKS Anywhere Bare Metal cluster on Dell PowerFlex Creating an Amazon EKS Anywhere Bare Metal cluster Validating the cluster deployment Installing the PowerFlex CSI driver Deployment tests and validation Amazon EKS Connector
Overview
Connecting an EKS Anywhere cluster to AWS EKS Connector
Amazon EKS Connector troubleshooting
Amazon EKS Connector Appendix
Conclusion Hardware qualification details References

Amazon EKS Connector troubleshooting

Amazon EKS Connector troubleshooting

  • Steps to troubleshoot the Amazon EKS Connector:

    1. Error loading GenericResouceCollection/Namespaces.

    Amazon EKS is unable to communicate with your Kubernetes cluster API server. The cluster must be in an ACTIVE state for successful connection. Try again in a few minutes.

    1. Run the following command to check for the connector pod status: 

    $ kubectl get pods -n eks-connector

    1. Run the following command to verify the Amazon EKS Connector logs:

    $ kubectl logs eks-connector-0 --container connector-init -n eks-connector

    $ kubectl logs eks-connector-1 --container connector-init -n eks-connector

    1. If the pod eks-connector-0 is not able to communicate with EKS-connector-1. Then delete and eks-connector pod and registered secret and reapply the Connector.yaml as follows:

    $ kubectl apply -f connector.yaml

    1. If you receive this error: An error occurred (SignatureDoesNotMatch) when calling the CreateRole operation: Signature not yet current: 20220826T144825Z is still later than 20220826T093628Z (20220826T092128Z + 15 min.)

    Run the following command to check the date and time on all the nodes and Amazon EKS connector pods.

    $ kubectl exec eks-connector-0 --container connector-agent -n eks-connector -- cat /var/log/amazon/ssm/amazon-ssm-agent.log 

    Stop and start the container service.

    1. If you get the following error: Error loading namespaces..users "arn:aws:iam::xxxxxxxxxxxxxxxxx" is forbidden: User "system:serviceaccount:eks-connector:eks-connector" cannot impersonate resource "users" in API group "" at the cluster scope.

    Download the YAML file and update it with %IAM_ARN% user field as follows:

    $ curl -o eks-connector-clusterrole.yaml https://s3.us-west-2.amazonaws.com/amazon-eks/eks-connector/manifests/eks-connector-console-roles/eks-connector-clusterrole.yaml

     

    $ kubectl apply -f eks-connector-clusterrole.yaml

    1. If you get the following error: Error loading namespaces: “Namespace is forbidden :user “users "arn:aws:iam::xxxxxxxxxxxxxxxxx"”cannot list resources “namespaces”in API group at the cluster.

    Download the YAML file and update the YAML with %IAM_ARN% user field as follows:

    $ curl -o eks-connector-console-dashboard-full-access-group.yaml https://s3.us-west-2.amazonaws.com/amazon-eks/eks-connector/manifests/eks-connector-console-roles/eks-connector-console-dashboard-full-access-group.yaml

     

    $ kubectl apply -f eks-connector-console-dashboard-full-access-group.yaml