33cc92efe2
When deleting cluster, Magnum only deletes the load balancers for Kubernetes services/ingresses before deleting Heat stack. The process of stack deletion is to delete resources in dependencies, which means, for Octavia resources, member is deleted first, then pool, listener, and finally load balancer. The whole process is error-prone, especially Octavia controller needs to talk to amphora for each API call before deleting load balancer, if any step fails, the deletion operation will fail. Octavia provides cascade deletion API[1] for the load balancer, which could delete all the related resources in one API call and doesn't involve communication between Octavia controller and amphora instance. This patch deletes the api/etcd load balancers (if applicable) before deleting Heat stack, making the cluster deletion process more robust. [1]: https://docs.openstack.org/api-ref/load-balancer/v2/index.html?expanded=remove-a-load-balancer-detail#remove-a-load-balancer story: 2007657 task: 39743 Change-Id: Ibe8f788559d0977475d0991fc99ad91ccfd7dca7
Team and repository tags
Magnum
Magnum is an OpenStack project which offers container orchestration engines for deploying and managing containers as first class resources in OpenStack.
For more information, please refer to the following resources:
- Free software: under the Apache license <http://www.apache.org/licenses/LICENSE-2.0>
- Wiki: https://wiki.openstack.org/wiki/Magnum_
- Documentation: https://docs.openstack.org/magnum/latest/
- Admin guide: https://docs.openstack.org/magnum/latest/admin/index.html
- Source: https://opendev.org/openstack/magnum
- Blueprints: https://blueprints.launchpad.net/magnum
- Bugs: https://storyboard.openstack.org/#!/project/openstack/magnum
- REST Client: https://opendev.org/openstack/python-magnumclient
- Release notes: https://docs.openstack.org/releasenotes/magnum/index.html
- Contributing: https://docs.openstack.org/magnum/latest/contributor/index.html