20bc89ff87
It is common for Neutron deployment's policy to forbid GETs to the public subnet, only allowing GETs for the public net. Since the only required field of those two for creating a FIP is the public net, let's change public net to be the only required config option and have the subnet stick around as optional. Change-Id: I31c3c51ad2dc12f8f560cbab01c86d04aabb754e Closes-Bug: 1749921 Signed-off-by: Antoni Segura Puimedon <antonisp@celebdor.com>
24 lines
876 B
YAML
24 lines
876 B
YAML
---
|
|
upgrade:
|
|
- |
|
|
|
|
For the external services (type=LoadBalancer) case,
|
|
a new field 'external_svc_net' was added and the 'external_svc_subnet'
|
|
field become optional.
|
|
The following should be modified at kuryr.conf::
|
|
|
|
|
|
[neutron_defaults]
|
|
external_svc_net= <id of external network>
|
|
# 'external_svc_subnet' field is optional, set this field in case
|
|
# multiple subnets attached to 'external_svc_net'
|
|
external_svc_subnet= <id of external subnet>
|
|
|
|
fixes:
|
|
- |
|
|
It is very common for production environments to only allow access
|
|
to the public network and not the associated public subnets.
|
|
In that case, we fail to allocate a floating IP to the Loadbalancer service
|
|
type.
|
|
In order to fix it, we added an option for specifying the network id instead
|
|
and switch the subnet config option to being optional. |