[Bug]: secret "milvus-operator-webhook-cert" not found #21961
Comments
Kellen-X
added
kind/bug
Kellen-X
changed the title
|
/assign @haorenfsa |
|
@Kellen-X Hi, thank you for this feedback. Could you tell me how did you install the milvus-operator? or which document did you follow? Or you can try follow the instructions in https://github.com/milvus-io/milvus-operator/blob/main/docs/installation/installation.md to install / update the milvus-operator again |
|
@haorenfsa
|
|
@Kellen-X Cloud you also provide the log of pod |
|
/unassign |
yanliang567
added
triage/accepted
kubectl logs -f milvus-operator-checker-fx4qq -n milvus-operator I0203 09:24:24.193250 1 request.go:668] Waited for 1.017843536s due to client-side throttling, not priority and fairness, request: GET:https://192.168.0.1:443/apis/milvus.io/v1beta1?timeout=32s |
|
@Kellen-X It seems that milvus-operator failed to install the cert-manager in your kubernetes due to the time out. You can try fix it by apply below yaml file with apiVersion: cert-manager.io/v1
kind: Issuer
metadata:
name: milvus-operator-selfsigned-issuer
namespace: milvus-operator
spec:
selfSigned: {}
---
apiVersion: cert-manager.io/v1
kind: Certificate
metadata:
name: milvus-operator-serving-cert
namespace: milvus-operator
spec:
dnsNames:
- milvus-operator-webhook-service.milvus-operator.svc
- milvus-operator-webhook-service.milvus-operator.svc.cluster.local
issuerRef:
kind: Issuer
name: milvus-operator-selfsigned-issuer
secretName: milvus-operator-webhook-cert |
@haorenfsa I use Alibaba Cloud products: "Alibaba Cloud Container Service for Kubernetes" (ack pro)
|
|
@Kellen-X Try deleting the old Certificate with |
kellen@kellendeMacBook-Pro milvus % kubectl get pods -n cert-manager kellen@kellendeMacBook-Pro milvus % kubectl apply -f https://raw.githubusercontent.com/milvus-io/milvus-operator/main/deploy/manifests/deployment.yaml --timeout=60s |
|
@Kellen-X I'm trying to reproduce it. I'll post the result here later. |
|
@Kellen-X Plz try The apiVersion: cert-manager.io/v1
kind: Issuer
metadata:
name: milvus-operator-selfsigned-issuer
namespace: milvus-operator
spec:
selfSigned: {}
---
apiVersion: cert-manager.io/v1
kind: Certificate
metadata:
name: milvus-operator-serving-cert
namespace: milvus-operator
spec:
dnsNames:
- milvus-operator-webhook-service.milvus-operator.svc
- milvus-operator-webhook-service.milvus-operator.svc.cluster.local
issuerRef:
kind: Issuer
name: milvus-operator-selfsigned-issuer
secretName: milvus-operator-webhook-cert |
|
|
Oh, cert-manager webhook has its own timeout config. Plz try this: kubectl patch mutatingwebhookconfigurations cert-manager-webhook --type='json' -p '[{"op": "replace", "path": "/webhooks/0/timeoutSeconds", "value": 30}]'
# then apply again
kubectl apply -f cert.yaml --timeout=30s |
|
If above still don't work, just delete it with
|
|
|
plz |
|
|
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
|
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
|
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Is there an existing issue for this?
Environment
Current Behavior
Expected Behavior
No response
Steps To Reproduce
No response
Milvus Log
No response
Anything else?
No response
The text was updated successfully, but these errors were encountered: