Skip to content
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 doesn't destroy the DigitalOcean load balancer #4

Open
imgrant opened this issue Feb 14, 2022 · 0 comments
Open

Terraform destroy doesn't destroy the DigitalOcean load balancer #4

imgrant opened this issue Feb 14, 2022 · 0 comments
Labels
wontfix This will not be worked on

Comments

@imgrant
Copy link
Owner

imgrant commented Feb 14, 2022

After following the fix in #3, terraform destroy completes but leaves behind an orphaned DigitalOcean load balancer.

The reason is that load balancer was deployed by adding the Kubernetes resource via flux, not via Terraform.
The solution is to remove the ingress-nginx Kubernetes resources before uninstalling flux (or manually delete the ingress-nginx resources via kubectl after flux has been uninstalled) and before using terraform destroy.

@imgrant imgrant added the wontfix This will not be worked on label Feb 14, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
wontfix This will not be worked on
Projects
None yet
Development

No branches or pull requests

1 participant