Comment 1 for bug 1976461

I can also confirm Octavia Amphora LB doesn't work as expected somehow only with Yoga deployment, but works with Xena or older deployments.

I'm following the OpenStack integration for k8s API endpoint.
https://ubuntu.com/kubernetes/docs/openstack-integration#api-server-load-balancer

For both releases (Yoga and Xena), Octavia Apmhora LB gets ACTIVE and ONLINE.

$ openstack loadbalancer list --format yaml
- id: e6277cf5-216d-4ed2-a285-dd1c73e799d1
  name: openstack-integrator-dfb7e924f5f7-kubernetes-control-plane
  operating_status: ONLINE
  project_id: 8d38f13076ff4c6ea7aafa6cd5948859
  provider: amphora
  provisioning_status: ACTIVE
  vip_address: 10.5.5.216

However, access to k8s API through Amphora works only with Xena deployment, but with Yoga deployment the connection times out.

### 192.168.151.52 is a FIP assigned to the LB
$ curl -vm 5 https://192.168.151.52:443/
* Trying 192.168.151.52:443...
* TCP_NODELAY set
* Connection timed out after 5000 milliseconds
* Closing connection 0
curl: (28) Connection timed out after 5000 milliseconds

My test deployment is based on openstack-base + octavia overlay:
https://github.com/nobuto-m/quick-maas/blob/1a2f307c0c1efcca88f0e8988f46967be5e024d0/user-script.sh#L150