MountVolume.SetUp failed for volume "bitwarden-tls-certs" : references non-existent secret key: ca.crt

[Tan-tan-san]

Steps To Reproduce

To Reproduce
Steps to reproduce the behavior:

1. Deployed sdk helm chart with 2 overrides:
   bitwarden-sdk-server.enabled: true
   certController.serviceAccount.name: external-secrets
   Other than that, everything else is default settings.
2. K8s version: v1.31.2+k3s1
3. helm chart repo: https://charts.external-secrets.io
4. Helm chart version: external-secrets:0.10.4
5. Images:
   -ghcr.io/external-secrets/bitwarden-sdk-server:v0.3.1
   -oci.external-secrets.io/external-secrets/external-secrets:v0.10.4

Expected Result

sdk pod deployement

Actual Result

the sdk pod failes to deploy with this error: MountVolume.SetUp failed for volume "bitwarden-tls-certs" : references non-existent secret key: ca.crt

Screenshots or Videos

No response

Additional Context

Additional context
Deploying the bitwarden-sdk server as required for ESO causes a problem where its looking for a ca.crt file along with the other tls files, but only the tls.cert and tls.key are created so there's no ca.crt file to access:

k describe secrets -n default bitwarden-tls-certs                                                                                                                                                       INT ✘  default ⎈ 
Name:         bitwarden-tls-certs
Namespace:    default
Labels:       controller.cert-manager.io/fao=true
Annotations:  cert-manager.io/alt-names: external-secrets.doin.science
              cert-manager.io/certificate-name: bitwarden-tls-certs
              cert-manager.io/common-name: external-secrets.doin.science
              cert-manager.io/ip-sans: 
              cert-manager.io/issuer-group: 
              cert-manager.io/issuer-kind: ClusterIssuer
              cert-manager.io/issuer-name: letsencrypt-prod
              cert-manager.io/uri-sans: 

Type:  kubernetes.io/tls

Data
====
tls.crt:  3610 bytes
tls.key:  1679 bytes

Operating System

Linux

Operating System Version

Ubuntu 22.04 LTS

Build Version

v0.3.1

Issue Tracking Info

• I understand that work is tracked outside of Github. A PR will be linked to this issue should one be opened to address it, but Bitwarden doesn't use fields like "assigned", "milestone", or "project" to track progress.