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
EKS nodepools can be now be tainted in the latest version of the Terraform AWS module ( see terraform-aws-modules/terraform-aws-eks#1403 ). On that basis, is there anything that is preventing us from moving from self-managed nodepools to managed nodepools ? This would make the EKS update process easier.
The text was updated successfully, but these errors were encountered:
We've started looking into this one. As we find out information we'll provide feedback. There will also be a PR with the code changes addressing this issue.
Has this been implemented now? It certainly looks as though the commit call d66d5b9 introduced key changes necessary to switch to the managed node groups (commit message seems to confirm this). The following output also suggests that to be the case: module.eks.module.eks_managed_node_group["cas"].aws_eks_node_group.this[0]: Still creating... [3m30s elapsed] module.eks.module.eks_managed_node_group["stateless"].aws_eks_node_group.this[0]: Still creating... [3m30s elapsed] module.eks.module.eks_managed_node_group["compute"].aws_eks_node_group.this[0]: Still creating... [3m30s elapsed] module.eks.module.eks_managed_node_group["default"].aws_eks_node_group.this[0]: Still creating... [3m30s elapsed]
Is there anything else pending to complete this request?
EKS nodepools can be now be tainted in the latest version of the Terraform AWS module ( see terraform-aws-modules/terraform-aws-eks#1403 ). On that basis, is there anything that is preventing us from moving from self-managed nodepools to managed nodepools ? This would make the EKS update process easier.
The text was updated successfully, but these errors were encountered: