You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When distributing CA certs through operator it should not copy the cert manager annotations in the vault tls secrets.
Actual Behavior
We are using cert manager to manage the certificates of all vault services in our kubernetes cluster.
When we are trying to create a namespace for our services, Banzai is automatically creating secret includes ca cert in that namespace, which is having cert manager annotations in the metadata of the secret resource and cert manager CA injector pod is complains that associated certificates resource with the secret is not present in that namespace.
cert-manager/secret-for-certificate-mapper "msg"="unable to fetch certificate that owns the secret" "error"="Certificate.cert-manager.io "vault" not found" "certificate"={"Namespace":"infra","Name":"vault"} "secret"={"Namespace":"infra","Name":"vault-tls"}
Steps To Reproduce
Install Banzai vault operator.
Use Cert manager to generate vault certificates.
Use "existingTlsSecretName: vault-tls" in the crd when bringing up the vault services.
Configuration
No response
Logs
Logs from the cert manager CA injector
cert-manager/secret-for-certificate-mapper "msg"="unable to fetch certificate that owns the secret""error"="Certificate.cert-manager.io "vault" not found""certificate"={"Namespace":"infra","Name":"vault"} "secret"={"Namespace":"infra","Name":"vault-tls"}
Additional Information
No response
The text was updated successfully, but these errors were encountered:
Preflight Checklist
Operator Version
v1.22.1
Installation Type
Helm
Bank-Vaults Version
v1.31.0
Kubernetes Version
v1.25.5
Kubernetes Distribution/Provisioner
rancher
Expected Behavior
When distributing CA certs through operator it should not copy the cert manager annotations in the vault tls secrets.
Actual Behavior
We are using cert manager to manage the certificates of all vault services in our kubernetes cluster.
When we are trying to create a namespace for our services, Banzai is automatically creating secret includes ca cert in that namespace, which is having cert manager annotations in the metadata of the secret resource and cert manager CA injector pod is complains that associated certificates resource with the secret is not present in that namespace.
cert-manager/secret-for-certificate-mapper "msg"="unable to fetch certificate that owns the secret" "error"="Certificate.cert-manager.io "vault" not found" "certificate"={"Namespace":"infra","Name":"vault"} "secret"={"Namespace":"infra","Name":"vault-tls"}
Steps To Reproduce
Configuration
No response
Logs
Additional Information
No response
The text was updated successfully, but these errors were encountered: