Maysa Macedo 11ccc66118 Prevent Kuryr restart due to connection issue ... In case the connection to Keystone is broken Kuryr controller is instantly restarted. This may result in leftovers loadbalancers as a Kubernetes service deletion can happen while the lbaas is still in PENDING_CREATE and if the controller is restarted, the deletion event will be gone. In this commit we give Kuryr a chance to retry the event before restarting. Change-Id: Ie2cacc86e745bbd7da7254f7adfd9b41370936ab Closes-bug: 1853460		2019-11-21 17:01:45 +00:00
..
__init__.py	Controller event handling pipeline	2016-11-03 13:08:29 +00:00
ingress_lbaas.py	Reuse utils.get_lbaas_spec in lb handler	2019-09-03 14:30:03 +09:00
kuryrnet.py	Ensure no KuryrNet addition is tried when namespace is not present	2019-10-04 14:26:42 +00:00
kuryrnetpolicy.py	Skip exception in case kuryrnetpolicy CRD is already deleted	2019-02-19 12:03:39 +01:00
lbaas.py	Avoid race between Retries and Deletion actions	2019-10-16 18:25:01 +02:00
namespace.py	Move from Neutron client to OpenStackSDK.	2019-10-23 14:08:18 +02:00
pipeline.py	Prevent Kuryr restart due to connection issue	2019-11-21 17:01:45 +00:00
pod_label.py	Avoid race between Retries and Deletion actions	2019-10-16 18:25:01 +02:00
policy.py	Merge "Ensure LB SG is not updated for egress only policy"	2019-11-12 16:27:37 +00:00
vif.py	Move from Neutron client to OpenStackSDK.	2019-10-23 14:08:18 +02:00