fix: Fix destruction failure when talking to EKS endpoint on private network #815
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
PR o'clock
Description
In #812 we have a situation where when one attempts to
terraform destroy
andcluster_endpoint_public_access
isfalse
then an error will be encountered: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 change has been tested with
cluster_endpoint_public_access
astrue
and asfalse
. I tested it by runningtf apply && tf destroy
in each case, verifying that it completed.Resolves #812
Checklist