karmada icon indicating copy to clipboard operation
karmada copied to clipboard

istio-ingressgateway 15012 port timeout

Open luoMonkeyKing opened this issue 2 years ago • 10 comments

What happened: When installing istio according to this document istio , the istio-ingressgateway of the member cluster reports that port 15012 has timed out, and the container network is now connected. image

karmada host istiod-elb image

When I telnet port 30359 in the member cluster, it is connected, but the telnet port 15012 in the member cluster is not connected

Environment:

  • Karmada version: 1.3
  • kubectl-karmada or karmadactl version (the result of kubectl-karmada version or karmadactl version): 1.3

luoMonkeyKing avatar Sep 28 '22 08:09 luoMonkeyKing

@zirain Can you help with it?

RainbowMango avatar Sep 28 '22 09:09 RainbowMango

The final solution is to restart the istiod in the karmada host, but the specific reason is not found. This is the second time I have encountered such a problem.

luoMonkeyKing avatar Sep 30 '22 07:09 luoMonkeyKing

There is one more question I want to ask, how do I open the application to the outside world, is the istio-ingressgateway to be deployed in the karmada host?

luoMonkeyKing avatar Sep 30 '22 07:09 luoMonkeyKing

There is one more question I want to ask, how do I open the application to the outside world, is the istio-ingressgateway to be deployed in the karmada host?

nop

zirain avatar Oct 09 '22 07:10 zirain

There is one more question I want to ask, how do I open the application to the outside world, is the istio-ingressgateway to be deployed in the karmada host?

nop

hi ,Does the gateway configuration need to be propagated to member cluster through pp? I only created the gateway configuration in the host cluster, which does not seem to take effect

luoMonkeyKing avatar Oct 09 '22 08:10 luoMonkeyKing

you should create it in karmada-apiserver

zirain avatar Oct 09 '22 13:10 zirain

you should create it in karmada-apiserver

you should create it in karmada-apiserver

yes, I created the gateway configuration in karmada-apiserver, and I also see the relevant configuration in the member cluster, but the error below the ingressgateway of the member cluster when accessing

"GET /productpage HTTP/1.1" 503 NC cluster_not_found - "-" 0 0 0 - "192.168.77.1" "curl/7.29.0" "c8e2a0fd-0a41-4c1c-8564-ce11939fcc2d" "192.168.77.1:32693" "-" - - 10.19.0.33:8080 192.168.77.1:47120 - -

luoMonkeyKing avatar Oct 11 '22 02:10 luoMonkeyKing

can you check the logs from ingressgateway and istiod? is everything ok?

zirain avatar Oct 11 '22 04:10 zirain

您可以检查来自ingressgateway 和istiod 的日志吗?一切都顺利吗?

member cluster istiod logs: image

member cluster ingressgateway logs: image

luoMonkeyKing avatar Oct 11 '22 04:10 luoMonkeyKing

您可以检查来自ingressgateway 和istiod 的日志吗?一切都顺利吗?

hi, the previous question should be the reason why the request is not added host, but I think the official case of istio does not need to be added. I plan to sort out the documents combining karmada and istiogateway later, and contribute to the community later

luoMonkeyKing avatar Oct 12 '22 11:10 luoMonkeyKing

As a lack of activity, let's close this first, feel free to reopen it if you still need it. /close

XiShanYongYe-Chang avatar Mar 04 '24 02:03 XiShanYongYe-Chang

@XiShanYongYe-Chang: Closing this issue.

In response to this:

As a lack of activity, let's close this first, feel free to reopen it if you still need it. /close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

karmada-bot avatar Mar 04 '24 02:03 karmada-bot