OpenStack integrator does not configure Neutron address pairs for LB VIPs or use a native LBaaSv2/Octavia for API load-balancing

Bug #1834327 reported by Dmitrii Shcherbakov on 2019-06-26
34
This bug affects 3 people
Affects Status Importance Assigned to Milestone
Kubernetes API Load Balancer
Undecided
Unassigned
Openstack Integrator Charm
Undecided
Unassigned

Bug Description

In order to use a virtual IPs for kube-api-loadbalancer (either with keepalived or with charm-hacluster) OpenStack integrator needs to set up Neutron such that it does not block VIP traffic for all ports of VMs that host kubeapi-load-balancer.

openstack port set <vm_port_uuid> --allowed-address <vip>

https://docs.openstack.org/python-openstackclient/queens/cli/command-objects/port.html#cmdoption-port-create-allowed-address

Alternatively (or in addition to that), LBaaS or Octavia could be utilized to load-balance Kubernetes master traffic instead.

description: updated
Nobuto Murata (nobuto) wrote :

This might/should be Juju's responsibility since that vip may need to be accessible for some hook executions. Relying on other charms such as openstack-integrator to modify the address pair may bring another race condition.

summary: OpenStack integrator does not configure Neutron address pairs for LB
- VIPs
+ VIPs or use a native LBaaSv2/Octavia for API load-balancing
Adam Israel (aisrael) on 2019-07-25
tags: added: osm
Ryan Beisner (1chb1n) on 2019-07-31
tags: added: uosci
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers