Maysa Macedo 9c2fcbc3e3 Fix SG rules on targetPort update ... After applying a Network Policy and updating an existent Service so that all 'targetPorts' are allowed by the policy, the SG rules are not being created with the required 'remote_ip_prefix'. Also, when the service is again updated with a 'targetPort' that is not allowed by the policy the respective SG rule is not deleted. This commit fixes the issue by associating 'targetPort' field to the 'LBaaSPortSpec' versioned object, which allows Kuryr to accounts for changes in not only 'name', 'port' and 'protocol' Kubernetes services' fields, but also 'targetPorts'. In addition, the LBaaS SG from the LBaaS state annotation is updated to match the SG stated in the LBaaS spec annotation, which has the updated SG to be applied. Closes-Bug: #1814920 Change-Id: Ifcdd1889a813c1eb078064facfb2ede83a179887		2019-02-18 10:05:44 +00:00
..
drivers	Merge "Handle exception raised in FIP allocation"	2019-02-01 20:29:33 +00:00
handlers	Fix SG rules on targetPort update	2019-02-18 10:05:44 +00:00
ingress	OCP-Router - Fix Ingress controller LB listener creation	2018-08-22 14:24:12 +03:00
managers	Avoid doing `raise ex` when only logging	2019-01-24 17:41:41 +01:00
__init__.py	Controller service base	2016-10-04 21:56:50 +03:00
service.py	Refactor DriverBase.get_instance()	2018-09-12 10:27:11 +09:00