-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
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
Terraform destroy being stuck #34
Comments
The issue is discussed in here aws/amazon-vpc-cni-k8s#69 |
It seems that configuration flag isn't available anymore. An alternative option would be to use delete time provisioners to delete all services on the cluster before its removal, but I don't think that would be a best practice Or maybe creating the ingress controller with the terraform so it will also remove those before removing the cluster. |
That means the ingress controller needs to be created after the infrastructure is ready, which seems to go against your proposal of merging cluster and config folders into one. |
I think we can have merging both folders and releasing an ingress controller via terraform. |
I remember there are a few reasons why NLB is a better choice than ALB: |
In our current setup with a ALB sit on top of the default Nginx controller that is installed via RADAR-Kubernetes, which isn't ideal but I think it mitigates the issue mentioned in the shared link. |
It's Known limitation mentioned in the README that
terraform destroy
won't work unlesshelmfile destroy
has been ran before. I don't think this is very practical and it's better if we find a solution for it.I searched the issue and it seems like there is a solution for it and the launch template of the node groups should be changed to auto delete the resources that are created by the EKS.
I'll update the issue when more information later.
The text was updated successfully, but these errors were encountered: