Getting N2_Read error when running fdbcli in a TLS enabled cluster on OCP

Using FoundationDB Kubernetes Operator
1

Hi,
I am very puzzle as to the cause of this, I notice that I am getting some N2_ReadError due to stream truncation whenever I run the fdbcli in any of the pods and then exit. Specifically, the error shown up when I exit fdbcli.



So, is that normal to get stream truncation whenever a disconnect occur?