使用Milvus配置nginx入口
本主題介紹如何使用 Milvus 配置 ingress nginx。 詳情請參閱ingress-nginx。
配置nginx入口
- 設置環境。
export DNS_LABEL="milvustest" # Your DNS label must be unique within its Azure location.
export NAMESPACE="ingress-basic"
- 安裝ngress nginx
helm repo add ingress-nginx https://kubernetes.github.io/ingress-nginx
helm repo update
helm install ingress-nginx ingress-nginx/ingress-nginx \
--create-namespace \
--namespace $NAMESPACE \
--set controller.service.annotations."service\.beta\.kubernetes\.io/azure-dns-label-name"=$DNS_LABEL \
--set controller.service.annotations."service\.beta\.kubernetes\.io/azure-load-balancer-health-probe-request-path"=/healthz
- 獲取外部 IP 位址。
kubectl --namespace $NAMESPACE get services -o wide -w ingress-nginx-controller
- 設定ngress控制器的FQDN。
# Public IP address of your ingress controller
IP="MY_EXTERNAL_IP"
# Get the resource-id of the public IP
PUBLICIPID=$(az network public-ip list --query "[?ipAddress!=null]|[?contains(ipAddress, '$IP')].[id]" --output tsv)
# Update public IP address with DNS name
az network public-ip update --ids $PUBLICIPID --dns-name $DNS_LABEL
# Display the FQDN
az network public-ip show --ids $PUBLICIPID --query "[dnsSettings.fqdn]" --output tsv
# sample output: milvustest.eastus2.cloudapp.azure.com
安裝 cert-manager
helm repo add jetstack https://charts.jetstack.io
helm repo update
helm install cert-manager jetstack/cert-manager \
--namespace $NAMESPACE \
--set installCRDs=true
建立 CA 叢集簽發器
- 使用下列範例清單建立叢集簽發器,例如 cluster-issuer.yaml。將 MY_EMAIL_ADDRESS 改為您組織的有效地址。
apiVersion: cert-manager.io/v1
kind: ClusterIssuer
metadata:
name: letsencrypt
spec:
acme:
server: https://acme-v02.api.letsencrypt.org/directory
email: MY_EMAIL_ADDRESS
privateKeySecretRef:
name: letsencrypt
solvers:
- http01:
ingress:
class: nginx
- 使用 kubectl apply 指令套用簽發器。
kubectl apply -f cluster-issuer.yaml
部署 Milvus
參考Azure,注意配置service.type
值,您需要變更為ClusterIP
。
建立 Milvus 入口路由
kubectl apply -f ingress.yaml
請參閱 ingress.yaml 的內容:
apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
name: my-release-milvus
annotations:
cert-manager.io/cluster-issuer: letsencrypt
nginx.ingress.kubernetes.io/backend-protocol: GRPC
nginx.ingress.kubernetes.io/force-ssl-redirect: "true"
nginx.ingress.kubernetes.io/proxy-body-size: 2048m
spec:
ingressClassName: nginx
tls:
- hosts:
- milvustest.eastus2.cloudapp.azure.com # the FQDN
secretName: tls-secret
rules:
- host: milvustest.eastus2.cloudapp.azure.com
http:
paths:
- path: /
pathType: Prefix
backend:
service:
name: my-release-milvus
port:
number: 19530
驗證
kubectl get certificate
NAME READY SECRET AGE
tls-secret True tls-secret 8m7s
kubectl get ingress
NAME CLASS HOSTS ADDRESS PORTS AGE
my-release-milvus nginx milvustest.eastus2.cloudapp.azure.com EXTERNAL-IP 80, 443 8m15s
你好 Milvus
請參考Hello Milvus,變更 uri args,然後執行程式碼。
connections.connect("default",uri="https://milvustest.eastus2.cloudapp.azure.com:443")