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
Please vote on this issue by adding a 馃憤 reaction to the original issue to help the community and maintainers prioritize this request
Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request
If you are interested in working on this issue or have submitted a pull request, please leave a comment
What is the outcome that you are trying to reach?
EKS BLUEPRINTS repo is soon deprecating sub-modules to create EKS node groups, fargate,kms, irsa, and emr on eks modules with an intention of leveraging open source aws modules.
As a part of this move all the doeks terraform blueprints will be migrated to use the latest v5 approach.
You will notice the major change is only for creating eks clusters, node groups and emroneks module. Kubernetes add-ons will still use the eks blueprints sub module.
Describe the solution you would like
Describe alternatives you have considered
Additional context
The text was updated successfully, but these errors were encountered:
Closing this issue. We will create a new tag and announce once all the blueprints are migrated with V5 approach. We will create issues with individual blueprints
Community Note
What is the outcome that you are trying to reach?
EKS BLUEPRINTS repo is soon deprecating sub-modules to create EKS node groups, fargate,kms, irsa, and emr on eks modules with an intention of leveraging open source aws modules.
As a part of this move all the doeks terraform blueprints will be migrated to use the latest v5 approach.
You will notice the major change is only for creating eks clusters, node groups and emroneks module. Kubernetes add-ons will still use the eks blueprints sub module.
Describe the solution you would like
Describe alternatives you have considered
Additional context
The text was updated successfully, but these errors were encountered: