PulsarHeartBeat and Bastion compnent failed to find "rootCaSecretName"

[yabinmeng]

When TLS is enabled and a customized root ca secrete name (e.g. tls-ss-ca) is provided (see below), PulsarHeartBeat and Bastion components failed to initialize with error "MountVolume.SetUp failed for volume "certs" : secret "tls-ss-ca" not found"

tls:
  ... ... 
   rootCaSecretName: "tls-ss-ca"

Checking the secrets, there is no ca certificate created with the customized name (e.g. 'tls-ss-ca'). However, a ca certificate with the default name 'pulsar-ss-ca' is created:

% kubectl get secrets | grep ss-ca
pulsar-ss-ca                                    kubernetes.io/tls                     3      7m32s