Twistlock defenders do not register with console

Bug

Description

We are deploying Twistlock console as a component of Big Bang. After the Twistlock license is installed and when the Twistlock defender daemonset is deployed, only the defender on the same RKE2 worker node is displayed in the Defender list in the Console UI. If the network policies in the twistlock namespace are deleted, the other defender pods register and are listed in the Console UI.

Provide any steps possible used to reproduce the error (ideally in an isolated fashion).

BigBang Version

1.11.0