Comment 4 for bug 1931594

An update on this:

- the cluster bind can be changed to control the default rule in haproxy
- new networks can be added in netplan and applied, haproxy will pick them because it's bound to 0.0.0.0
- new vips can be manually added to pacemaker using crm create resource, the charm will not wipe them when changing options (tested)
- DNS name for the new vips on other networks have to mimic dns name for official public one if you expect certificate to be automatically accepted

This should be enough to manually configure it until official support is implemented.