MetalLB speaker pods stuck in crashLoopBackOff missing '/etc/ml_secret_key/secretkey' file

Solution In Progress - Updated -

Issue

MetalLB speaker pods are stuck in crashLoopBackOff state due to error in speaker container:

{"caller":"main.go:126","error":"open /etc/ml_secret_key/secretkey: no such file or directory","level":"error","msg":"failed to read memberlist secret key file","op":"startup","ts":"2023-06-20T10:57:40Z"

Environment

  • Red Hat OpenShift Container Platform 4.11
  • Red Hat MetalLB Operator

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content