You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 7, 2022. It is now read-only.
We need to make sure the Lambda execution role is configured in the auth-auth ConfigMap of Amazon EKS in Account B.
Let's create a new Lambda role for Account A
Please note the Role Arn. We will use it later.
create Amazon EKS in Account B with eksctl
In account B
$ kubectl get no
NAME STATUS ROLES AGE VERSION
ip-192-168-44-190.ap-northeast-1.compute.internal Ready <none> 2m52s v1.12.7
ip-192-168-64-12.ap-northeast-1.compute.internal Ready <none> 2m55s v1.12.7
The text was updated successfully, but these errors were encountered: