We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The CreateAccessEntry API supports additional types that the module currently does not allow, in particular EC2 and HYPERPOD_LINUX.
EC2
HYPERPOD_LINUX
See: https://docs.aws.amazon.com/eks/latest/APIReference/API_CreateAccessEntry.html#AmazonEKS-CreateAccessEntry-request-type
At the moment, specifying on of the disallowed types results in a STANDARD access entry, which does not work when configuring the respective features.
For example, creating a custom node class for use with EKS Auto Mode requires an access entry of type EC2, https://docs.aws.amazon.com/eks/latest/userguide/create-node-class.html#auto-node-access-entry.
access_entries = { auto_mode = { principal_arn = module.cluster.node_iam_role_arn type = "EC2" policy_associations = { AmazonEKSAutoNodePolicy = { policy_arn = "arn:aws:eks::aws:cluster-access-policy/AmazonEKSAutoNodePolicy" access_scope = { type = "cluster" } } } } }
The text was updated successfully, but these errors were encountered:
fix: Adds support for access entry types EC2 and HYPERPOD_LINUX
5a75b5c
Closes terraform-aws-modules#3350
Nope, that wasn't it. My input wrapper was trashing the type, so it was picking up the default from from the try expression.
try
Sorry, something went wrong.
Successfully merging a pull request may close this issue.
Description
The CreateAccessEntry API supports additional types that the module currently does not allow, in particular
EC2
andHYPERPOD_LINUX
.See: https://docs.aws.amazon.com/eks/latest/APIReference/API_CreateAccessEntry.html#AmazonEKS-CreateAccessEntry-request-type
At the moment, specifying on of the disallowed types results in a STANDARD access entry, which does not work when configuring the respective features.
For example, creating a custom node class for use with EKS Auto Mode requires an access entry of type
EC2
, https://docs.aws.amazon.com/eks/latest/userguide/create-node-class.html#auto-node-access-entry.Versions
Reproduction Code [Required]
The text was updated successfully, but these errors were encountered: