Pools are not aware of ports subnet
Bug #1752600 reported by
Luis Tomas Bolivar
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
kuryr-kubernetes |
Fix Released
|
High
|
Luis Tomas Bolivar |
Bug Description
By now there is only one subnet driver that always forces pods to use the same Neutron subnet. However, if a new subnet driver is added allowing pods to be on different networks, the pool drivers may misbehave as the current key used to differentiate between the pools does not include information about the network. This could lead to assigning a wrong port (from the wrong network) to a pod, as they can share the other components of the pool-key: hostIP/hostname, project_id and security groups.
Changed in kuryr-kubernetes: | |
assignee: | nobody → Luis Tomas Bolivar (ltomasbo) |
status: | New → In Progress |
Changed in kuryr-kubernetes: | |
importance: | Undecided → High |
To post a comment you must log in.
Reviewed: https:/ /review. openstack. org/548673 /git.openstack. org/cgit/ openstack/ kuryr-kubernete s/commit/ ?id=bc7e9000829 9a856f951e895c7 00362b74fb3d67
Committed: https:/
Submitter: Zuul
Branch: master
commit bc7e90008299a85 6f951e895c70036 2b74fb3d67
Author: Luis Tomas Bolivar <email address hidden>
Date: Wed Feb 28 17:22:44 2018 +0000
Add network id to pools keys
This is one of the first steps needed to have pools support when hostname, project_id and security groups.
pods can be allocated on different networks. Otherwise, a common
pool could serve pods on different networks if they share
hostIP/
Closes-Bug: 1752600 76afc125f0d3af5 0d1bd2f3eff
Change-Id: If9c8e898ec7115