Description
During certificate renewals and replacement of private keys, the Cluster CA secret might contain more than one public key. The operands need to load all of them to be able to work during the rollouts when the other components might be using both the old and new certificate (they will always use only one of them, but e.g. one broker might already have the new while other has still the old).
This currently does not happen and the Exporter uses only the ca.crt file. As a result, during Cluster CA key replacement, it will start crash-looping instead of rolling smoothly.