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
Error: invalid access entry type "EC2" for accessEntries[0]
Why do you want this feature?
If you want to create access entry to authorize node role for Auto Mode, you must specify "EC2" type. This is useful when you want to use your own non-default NodeClass and NodePools. This entry is normally created automatically, but if you disable built-in node pools (set them as empty array), eksctl will throw an error if you specify nodeRoleARN, so you have to use accessConfig, which also currently doesn't work.
Note that it is possible to do with aws cli, e.g. this will work:
What feature/behavior/change do you want?
When defining access entries, type "EC2" type should be allowed to integrate with Auto Mode.
Note: this is different from "EC2_LINUX".
Example manifest:
Currently (
0.199.0
), this throws an error:Why do you want this feature?
If you want to create access entry to authorize node role for Auto Mode, you must specify "EC2" type. This is useful when you want to use your own non-default NodeClass and NodePools. This entry is normally created automatically, but if you disable built-in node pools (set them as empty array), eksctl will throw an error if you specify nodeRoleARN, so you have to use accessConfig, which also currently doesn't work.
Note that it is possible to do with aws cli, e.g. this will work:
Alternative solution
Allow to specify
autoModeConfig.nodeRoleARN
even withnodePools: []
, and create the correct association based on specified role.The text was updated successfully, but these errors were encountered: