Controller doesn't delete LB if wrong floating subnet was set in a Service
Bug #1813015 reported by
livelace
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
kuryr-kubernetes |
Fix Released
|
Undecided
|
Yossi Boaron |
Bug Description
Openstack version: Queens, LBaaS v2 (legacy)
Kuryr version: Docker latest
Openshift/
Description:
If a Service has externalIP value which _doesn't belong_ to Openstack floating subnets:
1. Service is created: Load Balancer is created and works, pass traffic to Pod as expected.
2. Service is deleted: Load Balancer still persist, not expected.
This problem was appeared during a deployment of Jenkins Helm chart(https:/
Changed in kuryr-kubernetes: | |
assignee: | nobody → Yossi Boaron (yossi-boaron-1234) |
To post a comment you must log in.
Hi Livelace,
Could you please attach the relevant k8s service manifest (jenkins- 79bd456cb4- 89kcz)?