Installation failed with existent cert-manager on EKS

[riosje]

Hi, I've installed the operator following this instructions, for environments with existent cert-manager(v1.14.4) implementation
https://github.com/zilliztech/milvus-operator/blob/main/docs/installation/installation.md#installation

helm install milvus-operator \
  -n milvus-operator --create-namespace \
  https://github.com/zilliztech/milvus-operator/releases/download/v0.9.13/milvus-operator-0.9.13.tgz \
  --set checker.disableCertManagerCheck=true

Issue

The pods are stuck on ContainerCreating

  Type     Reason       Age                   From               Message
  ----     ------       ----                  ----               -------
  Normal   Scheduled    5m49s                 default-scheduler  Successfully assigned milvus-operator/milvus-operator-6c88644565-klhpn to ip-10-30-4-20.us-west-2.compute.internal
  Warning  FailedMount  98s (x10 over 5m48s)  kubelet            MountVolume.SetUp failed for volume "cert" : secret "milvus-operator-webhook-cert" not found

ERROR
MountVolume.SetUp failed for volume "cert" : secret "milvus-operator-webhook-cert" not found

Should I create another resource, what part am I missing?

Thank you so much for your help.

[riosje]

As far as I can see, it is trying to mount a secret with a cert, but there is not such secret.
does the helm chart should create that resource? or should I create it?

[haorenfsa]

@riosje The secret should be created by cert-manager in regular procedure. I doubt if the cert-manager is working correctly.

It seems very close to this issue milvus-io/milvus#21961.

If you still can't solve it please provide me the logs of cert-manager.