+++ This bug was initially created as a clone of Bug #1626377 +++ When creating a listener for an octavia loadbalancer, for example opening port 80, it opens that port for accessing from everywhere by creating a security group that allows that traffic from 0.0.0.0/0. However, it may be needed to just enable access to that port from a given subnet or from pods with a given security group, similarly how it is done with VMs. Currently it is not possible to do so, as the security group generated for the listener/loadbalancer does not belong to the tenant that created the loadbalancer but to the admin. There are several ways in which this could be fix: - Creating loadbalancer resources within the tenant instead (perhaps only the VIP port and the associated security group will be enough). - Extending listener creation API to include extra options similar to what security groups has. - Add the option in Octavia to add extra security groups to the amphora by the tenant who created it, that will allow extra customization on the access to the loadbalancer.
Re-setting Target Milestone z1 to --- to begin the 15z1 Maintenance Release.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2019:2957