-
-
Notifications
You must be signed in to change notification settings - Fork 4.1k
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
kubernetes_config_map
causing terraform destroy to fail?
#812
Comments
This takes place across AWS accounts, and with or without node groups or worker ASGs (just sharing though I do not think it relevant). |
Could this be related to #745 that you are pinned to? It creates a security group rule when Output from the destroy command would help to debug. |
Good points, @dpiddockcmp, and thank you. :) A newer commit fixed the issue.
I should have tested that before opening a ticket while half asleep. |
Just encountered it again but this type on commit
|
Encounter the error on plan and apply now too. I'm thinking through why. I have checked my connection to the internet. :) |
Could it be because the endpoint is a private IP since I am on the VPC network via a VPN and the rules that allow communication with the API are removed prior to the command to destroy the config map?
Yes, it did just occur to me that I did not share that I was on a VPN that can communicate with the AWS VPC. :/ |
Yes, very much is the new security rule. There is no dependency between it and the
Does not present as an issue when creating the cluster due to the |
Ok, I created a PR to fix this if it passes review. |
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further. |
I have issues
I'm submitting a...
What is the current behavior?
Terraform destroy reliably results in
Error: Get https://SNIP.eks.amazonaws.com/api/v1/namespaces/kube-system/configmaps/aws-auth: dial tcp IP:443: i/o timeout
(IP:443
is the IP of the endpoint). This occurs across AWS accounts. Could be something I have done.If this is a bug, how to reproduce? Please include a code sample if relevant.
What's the expected behavior?
Destroy happen without error on this resource.
Are you able to fix this problem and submit a PR? Link here if you have already.
I work around the issue by running
terraform state rm 'module.eks.module.eks.kubernetes_config_map.aws_auth[0]'
.Environment details
9951c87a86b02e0f61a4d1560ad2e6e9596000ed
, but not in v10.0.0.Any other relevant info
I may be causing this with some configuration or it may be a new behavior. I am willing to help. :)
The text was updated successfully, but these errors were encountered: