Timeline for Cannot configure node group in new EKS cluster due to no Node IAM role found
Current License: CC BY-SA 4.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 1, 2023 at 9:47 | comment | added | Tim Malone | Ah... the refresh button next to the role list only pretends to refresh the roles. You have to actually hard refresh the page to see newly created roles. 🤦♂️ | |
| Apr 1, 2023 at 9:28 | comment | added | Tim Malone | Technically the role gets assumed by EC2 rather than EKS. Having said that I'm still having the issue the OP described even after following the documentation (and double checking with your answer). There must be something else somewhere that causes a problem with this in some situations... | |
| Feb 20, 2021 at 4:48 | comment | added | CairoCoder | update the policy under "Trust Relationships". | |
| Nov 20, 2020 at 12:41 | history | edited | Recoba20 | CC BY-SA 4.0 |
deleted 445 characters in body
|
| Nov 18, 2020 at 9:42 | history | edited | Recoba20 | CC BY-SA 4.0 |
added 348 characters in body
|
| May 30, 2020 at 10:54 | vote | accept | Mugen | ||
| May 29, 2020 at 21:48 | history | answered | Recoba20 | CC BY-SA 4.0 |