-
Notifications
You must be signed in to change notification settings - Fork 3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug]: Unable to create a Milvus Cluster in K8s #37430
Comments
/assign @haorenfsa |
Hi @knowitall12, could you also provide me with the log of milvus-operator when the error happened? |
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. |
version: 1.1.4 |
Is there an existing issue for this?
Environment
Current Behavior
We have deployed Cert-manager, milvus-operator using the documentation at: https://milvus.io/docs/v2.3.x/install_cluster-milvusoperator.md. Now while deploying the milvus cluster using below script we are getting error.
Error: Error from server (InternalError): error when creating "milvus-cluster.yaml": Internal error occurred: failed calling webhook "mmilvus.kb.io": failed to call webhook: Post "https://milvus-operator-webhook-service.milvus-operator.svc:443/mutate-milvus-io-v1beta1-milvus?timeout=10s": Address is not allowed
Cert-manager and milvus-operator pods are also in running status.
Expected Behavior
Should be able to deploy the cluster.
Steps To Reproduce
No response
Milvus Log
Error from server (InternalError): error when creating "milvus-cluster.yaml": Internal error occurred: failed calling webhook "mmilvus.kb.io": failed to call webhook: Post "https://milvus-operator-webhook-service.milvus-operator.svc:443/mutate-milvus-io-v1beta1-milvus?timeout=10s": Address is not allowed
Anything else?
No response
The text was updated successfully, but these errors were encountered: