External service routing support: HTTP 404 upon accessing /console/api/setup

[jieliang02]

Describe the bug
A clear and concise description of what the bug is.

To Reproduce
Steps to reproduce the behavior:

1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error

Expected behavior
A clear and concise description of what you expected to happen.

Screenshots

Desktop (please complete the following information):
kylin v10 sp2
dify-helm-dify-0.23.0-rc2.tar

Additional context
I have reviewed the relevant documents, but my issue has not been resolved. The VirtualService resource in the document has not been created. I'm not sure where the problem comes from, can you please help me
#122

[jieliang02]

[root@10-29-224-44 daocloud]# kubectl -n dify get pod,svc
NAME READY STATUS RESTARTS AGE
pod/dify-api-6d76d7dcf9-pdlfc 1/1 Running 0 81m
pod/dify-plugin-daemon-5d7987545b-s942h 1/1 Running 0 81m
pod/dify-postgresql-primary-0 1/1 Running 0 100m
pod/dify-postgresql-read-0 1/1 Running 0 100m
pod/dify-proxy-5d48d7fdb4-cxrl8 1/1 Running 0 81m
pod/dify-redis-master-0 1/1 Running 0 100m
pod/dify-redis-replicas-0 1/1 Running 0 100m
pod/dify-redis-replicas-1 1/1 Running 0 99m
pod/dify-redis-replicas-2 1/1 Running 0 98m
pod/dify-sandbox-7bd556b48f-txjx4 1/1 Running 0 81m
pod/dify-web-7bcbf94b6f-29585 1/1 Running 0 81m
pod/dify-worker-db59766f8-69c6t 1/1 Running 0 81m
pod/helm-operation-uninstall-dify-5kscdxq4v4-c4th8 0/1 Completed 0 133m
pod/helm-operation-uninstall-dify-7cd8qxrp78-gdwlz 0/1 Completed 0 131m
pod/helm-operation-uninstall-dify-8v5gswk6rg-7nrqn 0/1 Completed 0 161m
pod/helm-operation-uninstall-dify-9z5jjmm8wt-rpwlk 0/1 Completed 0 7h25m
pod/helm-operation-uninstall-dify-bmf7vkmjnj-wtjc7 0/1 Completed 0 123m
pod/helm-operation-uninstall-dify-qnnn9lcz6c-4h9fl 0/1 Completed 0 6h6m
pod/helm-operation-uninstall-dify-v74vbrd65m-cscq2 0/1 Completed 0 139m
pod/helm-operation-uninstall-dify-x9twxzpm4q-8kgm2 0/1 Completed 0 127m
pod/weaviate-0 1/1 Running 0 99m
pod/weaviate-1 1/1 Running 0 99m
pod/weaviate-2 1/1 Running 0 99m

NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
service/dify ClusterIP 10.233.51.169 80/TCP 113m
service/dify-api ClusterIP 10.233.32.127 5001/TCP 113m
service/dify-plugin-daemon ClusterIP 10.233.4.94 5002/TCP 113m
service/dify-postgresql-primary ClusterIP 10.233.54.208 5432/TCP 113m
service/dify-postgresql-primary-hl ClusterIP None 5432/TCP 113m
service/dify-postgresql-read ClusterIP 10.233.36.247 5432/TCP 113m
service/dify-postgresql-read-hl ClusterIP None 5432/TCP 113m
service/dify-redis-headless ClusterIP None 6379/TCP 113m
service/dify-redis-master ClusterIP 10.233.39.64 6379/TCP 113m
service/dify-redis-replicas ClusterIP 10.233.51.193 6379/TCP 113m
service/dify-sandbox ClusterIP 10.233.41.103 8194/TCP 113m
service/dify-web NodePort 10.233.42.164 3000:31649/TCP 113m
service/weaviate ClusterIP 10.233.54.171 80/TCP 113m
service/weaviate-headless ClusterIP None 80/TCP 113m
[root@10-29-224-44 daocloud]#

[BorisPolonsky]

There are known issues in 0.23.0-rc2 so it's not advised to be deployed in the current state.

[jieliang02]

Hello brother, I noticed that you have released a new version (dify-0.23.0-RC3), but this issue still persists. Why is this

[BorisPolonsky]

This issue is unlikely a bug from the chart. We'd suggest you validate this api in component api first.

kubectl exec -it -n <namespace> <api-pod-name> -- curl localhost:5001/console/api/setup

Then you should check if service routing on your cluster works as expected when it comes to external service access. Without knowing how you exposed each of the microservices beyond the cluster there's no way to figure out what the underlying problem is.

[jieliang02]