Open
Description
MetalLB Version
0.14.8
Deployment method
Charts
Main CNI
k3s (not sure what it uses)
Kubernetes Version
1.30.6+k3s1
Cluster Distribution
k3s
Describe the bug
When enabling the readiness and liveness probes in the helm chart, the frr container never becomes healthy. The only way to have the pods start is to disable the probes completely.
This is similar to #1926 which was apparently fixed but I've kept my helm chart updated and I still get this issue
To Reproduce
- Install helm chart
- Enable liveness/readliness probes
- The speaker pods never start and become healthy
Expected Behavior
Pods start and become ready
Additional Context
I can't get debug logs when it does this because the pods don't start so I can't get into them :/
I've read and agree with the following
- I've checked all open and closed issues and my request is not there.
- I've checked all open and closed pull requests and my request is not there.
I've read and agree with the following
- I've checked all open and closed issues and my issue is not there.
- This bug is reproducible when deploying MetalLB from the main branch
- I have read the troubleshooting guide and I am still not able to make it work
- I checked the logs and MetalLB is not discarding the configuration as not valid
- I enabled the debug logs, collected the information required from the cluster using the collect script and will attach them to the issue
- I will provide the definition of my service and the related endpoint slices and attach them to this issue