Closed Kristian-ZH closed 6 months ago
Thanks for this @Kristian-ZH - I'm asking @atanasdinov to take a look also as we need to validate functionality for multi-node k8s as we use this for establishing multi-node clusters via EIB.
@atanasdinov you can test it with this helm repo: https://kristian-zh.github.io/charts
I think that changing the repo here: https://github.com/suse-edge/edge-image-builder/blob/11e1493efb174de12464e2c2379a43714e5b0010/pkg/combustion/templates/k8s-vip.yaml.tpl#L20
and then the version to 0.14.3
is enough
I didn't know that the repository is transferred over for forks. Thanks!
It is not, I published it now and linked it to the PR branch :D
I upgraded to 0.14.3 and re-deployed a CAPI cluster via Metal3 and all worked:
shardy@localhost:~/metal3-demo-files> helm list -n metallb-system
NAME NAMESPACE REVISION UPDATED STATUS CHART APP VERSION
metallb metallb-system 2 2024-03-07 11:51:42.708493747 +0000 UTC deployed metallb-0.14.3 v0.14.3
shardy@localhost:~/metal3-demo-files> kubectl get bmh
NAME STATE CONSUMER ONLINE ERROR AGE
controlplane-0 provisioned sample-cluster-controlplane-lpqfq true 19h
worker-0 provisioned sample-cluster-workers-lv2cr true 19h
Align MetalLB with the upstream version: v0.14.3.
This PR also introduces a new component called
frr-k8s
- https://github.com/metallb/frr-k8s