We have run into the issue during deployment where the wrong private key is still being used by the broker pod or the key pair has changed. It would be a helpful feature if the message broker ran a simple check at the start to send a encrypted message to itself to see if the key pair is valid, or if it just grabs the public key from the hub and checks if there is a mismatch with the private key it is reading. Currently, we have to create an analysis and start it at two different nodes to check for this error
We have run into the issue during deployment where the wrong private key is still being used by the broker pod or the key pair has changed. It would be a helpful feature if the message broker ran a simple check at the start to send a encrypted message to itself to see if the key pair is valid, or if it just grabs the public key from the hub and checks if there is a mismatch with the private key it is reading. Currently, we have to create an analysis and start it at two different nodes to check for this error