To reduce the amount of workload Kuryr puts on Neutron, the way Kuryr handle Kubernetes Namespace and Pods can be revisited to avoid the following scenarios:

• Networks and Subnets created for Namespaces that only contain hostNetworking Pods
• Network and Subnets created for Namespaces without Pods
• Pods with status Completed having Neutron Ports still assigned
• Neutron Ports with DOWN status removed from Kuryr ports pool, but not removed from Neutron

As part of this epic we should also revisit batch APIs requests that we made to Neutron team long time ago. E.g. cascade delete of networks would improve our lives very much.