Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

liveness and readiness probes in helm chart appear to be broken for frr container #2628

Open
8 tasks done
2fst4u opened this issue Dec 7, 2024 · 0 comments
Open
8 tasks done
Labels

Comments

@2fst4u
Copy link

2fst4u commented Dec 7, 2024

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

  1. Install helm chart
  2. Enable liveness/readliness probes
  3. 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
@2fst4u 2fst4u added the bug label Dec 7, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant