Hi @cynerva, hacluster also has the same effect and we orientation is to use hacluster instead of keepalived.
When we look for OpenStack bundles, each openstack service has a os-*-hostname option (where * is public, private or admin).
That is set on the charms themselves. Maybe, that should be the approach for k8s charms as well.
Hi @cynerva, hacluster also has the same effect and we orientation is to use hacluster instead of keepalived.
When we look for OpenStack bundles, each openstack service has a os-*-hostname option (where * is public, private or admin).
That is set on the charms themselves. Maybe, that should be the approach for k8s charms as well.