6d43ad4c78
When a namespace is deleted, kuryr-controller is in charge of deleting its associated openstack resources (net, subnet and ports) as well as the associated KuryrNet CRD. As removing OpenStack resources may take some time, if the kuryr-controller is restarted by any different reason during that process, the resources will be left behind as no new events for the namespace (already deleted) will happen after the restart. This patch fixes this problem by ensuring upon reboot that there are no orphan KuryrNet CRDs for unexisting namespaces, and deleting them in case there are (including its associated OpenStack resources). Closes-Bug: 1848761 Change-Id: I0c4852f5bb816756cc1bf536354da20aa3948dc7 |
||
---|---|---|
.. | ||
__init__.py | ||
ingress_lbaas.py | ||
kuryrnet.py | ||
kuryrnetpolicy.py | ||
lbaas.py | ||
namespace.py | ||
pipeline.py | ||
pod_label.py | ||
policy.py | ||
vif.py |