In the case when two ports with same targetport are created, if only one of the targetPorts is updated the unused member(s) from the respective pool is not removed and the new ones are added.
For example, if the following spec is applyed:
apiVersion: v1
kind: Service
metadata:
name: demo-test2
spec:
ports:
- port: 80
name: port-80
protocol: TCP
targetPort: 8080
- port: 443
name: port-443
protocol: TCP
targetPort: 8080
selector:
app: demo
type: ClusterIP
and then the target port of one of them is modified, the resulted members will be:
$ openstack loadbalancer member list 950464ff-31fa-49da-ae56-2a7742d036cb
+--------------------------------------+------------------------------------+----------------------------------+---------------------+------------+---------------+------------------+--------+
| id | name | project_id | provisioning_status | address | protocol_port | operating_status | weight |
+--------------------------------------+------------------------------------+----------------------------------+---------------------+------------+---------------+------------------+--------+
| 73f07d84-65cc-4ba6-85b3-f4a8cf10fe3d | default/demo-58c4c6895c-rq5hx:8080 | 1d7834dbe86d4d3f81b697f95bec0c13 | ACTIVE | 10.0.0.208 | 8080 | NO_MONITOR | 1 |
| 9a849eec-b9bc-4bd3-94b2-97ac26e1f7dc | default/demo-58c4c6895c-khpvt:8080 | 1d7834dbe86d4d3f81b697f95bec0c13 | ACTIVE | 10.0.0.222 | 8080 | NO_MONITOR | 1 |
| 642ceb73-f82d-462c-a46c-fa86beb87bf3 | default/demo-58c4c6895c-rq5hx:8090 | 1d7834dbe86d4d3f81b697f95bec0c13 | ACTIVE | 10.0.0.208 | 8090 | NO_MONITOR | 1 |
| d3dd8189-555b-4810-a43f-7e73030e61b0 | default/demo-58c4c6895c-khpvt:8090 | 1d7834dbe86d4d3f81b697f95bec0c13 | ACTIVE | 10.0.0.222 | 8090 | NO_MONITOR | 1 |
+--------------------------------------+------------------------------------+----------------------------------+---------------------+------------+---------------+------------------+--------+
When should be:
$ openstack loadbalancer member list 950464ff-31fa-49da-ae56-2a7742d036cb
+--------------------------------------+------------------------------------+----------------------------------+---------------------+------------+---------------+------------------+--------+
| id | name | project_id | provisioning_status | address | protocol_port | operating_status | weight |
+--------------------------------------+------------------------------------+----------------------------------+---------------------+------------+---------------+------------------+--------+
| 642ceb73-f82d-462c-a46c-fa86beb87bf3 | default/demo-58c4c6895c-rq5hx:8090 | 1d7834dbe86d4d3f81b697f95bec0c13 | ACTIVE | 10.0.0.208 | 8090 | NO_MONITOR | 1 |
| d3dd8189-555b-4810-a43f-7e73030e61b0 | default/demo-58c4c6895c-khpvt:8090 | 1d7834dbe86d4d3f81b697f95bec0c13 | ACTIVE | 10.0.0.222 | 8090 | NO_MONITOR | 1 |
+--------------------------------------+------------------------------------+----------------------------------+---------------------+------------+---------------+------------------+--------+
If both targetPorts are updated with same value in the service spec the correct members are presented in the pool.
Fix proposed to branch: master
Review: https:/