Bug Description
I integrated (via Helm) an OCCM on a k8s cluster and I created a loadbalancer. I thought I could use load-balancer-cidrs and load-balancer-enabled to specify a specific ip to use for the loadbalancer.
However, these configs seem to force the use of metallb
To Reproduce
-Deploy a k8s charm with load-balancer-enabled and load-balancer-cidrs unset
- Integrate with OCCM
- Set load-abalncer-cidrs and load-balancer-enabled
- You will notice a new metallb-system namepsace created
- Create a loadbalancer (could be traefik's in cos-lite)
- Describe the created service. You will see that is a metallb
Environment
Charmed Yoga. 1.32 k8s cluster (via the k8s charm) on top (the nodes are openstack VMs) then integrate OCCM (2.32) via Helm
Relevant log output
Additional context
No response
Bug Description
I integrated (via Helm) an OCCM on a k8s cluster and I created a loadbalancer. I thought I could use
load-balancer-cidrsandload-balancer-enabledto specify a specific ip to use for the loadbalancer.However, these configs seem to force the use of metallb
To Reproduce
-Deploy a k8s charm with load-balancer-enabled and load-balancer-cidrs unset
Environment
Charmed Yoga. 1.32 k8s cluster (via the k8s charm) on top (the nodes are openstack VMs) then integrate OCCM (2.32) via Helm
Relevant log output
.Additional context
No response