search

Azure / ACS

Azure Container Service - Bug Tracker + Announcements
65 stars 27 forks source link

Deleting Container Service leaves provisioned resources around #31

Open tombuildsstuff opened 7 years ago

tombuildsstuff commented 7 years ago

Migrating this from https://github.com/Azure/acs-engine/issues/792

Ciao!

When provisioning an Azure Container Service instance through the API - lots of resources are created for things like Storage Accounts, VMSS etc, through what appears to be an ARM Template. When deleting the Container Service instance through the API these resources aren't cleared up - which we've had come through as issue https://github.com/terraform-providers/terraform-provider-azurerm/issues/79

Would it be possible to fix this? Thanks! :)

Orchestrator and version (e.g. Kubernetes, DC/OS, Swarm) I tried DC/OS, using the top example on this page, but I'm assuming this is applicable to all.

What happened: The Container Service got deleted, but all the provisioned resources got left behind.

What you expected to happen: The resources provisioned by Azure Container Service would be cleaned up when deleting the Container Service instance.

How to reproduce it (as minimally and precisely as possible): Delete the Container Service instance through the Azure API (we do this via terraform destroy --target=azurerm_container_service.test, but just a regular API call will work)

Anything else we need to know:

This bug was originally https://github.com/hashicorp/terraform/issues/14128 before migrating to the new location: https://github.com/terraform-providers/terraform-provider-azurerm/issues/79

JackQuincy commented 7 years ago

This is a known limitation at this point. We have a rev of the service in the works that will provision the resources in a new resource group and delete the resource group when you delete the service but that is still a ways out and won't help with old clusters. ETA on that is still unknown.

vchan2002 commented 7 years ago

Thanks for your input! It does appear that, when the ACS service is setup, it considers the resources it creates a part of the resource group, not as the ACS Service. At this point, I do think the only way those resource will go away is to destroy the resource group.

JackQuincy commented 7 years ago

If there isn't something else in the resource group you want to keep around that is by far the easiest way to clean up.

JackQuincy commented 7 years ago

We recently deployed a new version of the Service in the UK and that version will correctly clean up these resources.

tombuildsstuff commented 7 years ago

@JackQuincy awesome, thanks - I'll ask the original reporter to try this in one of the UK Data Centres and confirm this solves their issue. Any idea when that will be rolled out globally? Thanks!

JackQuincy commented 7 years ago

No ETA. but it is what we are actively working on. this is the announcement of the change in the uk https://github.com/Azure/ACS/blob/master/announcements/2017-06-28-acs-uk-public-preview.md . Some limitations to know. Even after we go global this behavior will only take effect on new clusters.