Skip to content

failed to access when deploying waypoints of various granulairties in a mixed manner #691

@YaoZengzeng

Description

@YaoZengzeng

What happened:

We have just fixed the inaccessibility issuse when deploy waypoint in ns granularity #628

But I include both ns granularity and svc granularity waypoint in the same ns, such as:

root@kurator-linux-0002:~# kgp
NAME                                    READY   STATUS    RESTARTS   AGE
details-v1-cdd874bc9-fb6j6              1/1     Running   0          4h55m
productpage-v1-5bb9985d4d-9rxpd         1/1     Running   0          4h55m
ratings-v1-6484d64bbc-vfcpg             1/1     Running   0          4h55m
reviews-svc-waypoint-6884756fc5-mplbb   1/1     Running   0          11m
reviews-v1-598f9b58fc-rb5d5             1/1     Running   0          4h55m
reviews-v2-5979c6fc9c-7c4wd             1/1     Running   0          4h55m
reviews-v3-7bbb5b9cf7-jnvlk             1/1     Running   0          4h55m
sleep-5577c64d7c-tz6zr                  1/1     Running   0          4h55m
tcp-echo-svc-waypoint-7578fb9d5-zs9t5   1/1     Running   0          4h55m
tcp-echo-v1-55dbb9bcb-5ndph             1/1     Running   0          4h55m
tcp-echo-v2-77c855674c-wpzxp            1/1     Running   0          4h55m
waypoint-7cd5f44d8f-zjsd8               1/1     Running   0          4h55m
root@kurator-linux-0002:~# kubectl  get gateway
NAME                    CLASS            ADDRESS        PROGRAMMED   AGE
reviews-svc-waypoint    istio-waypoint   10.96.48.220   True         12m
tcp-echo-svc-waypoint   istio-waypoint   10.96.1.132    True         24h
waypoint                istio-waypoint   10.96.62.79    True         5h3m

We deployed the ns granularity waypoint called waypoint and also deployed waypoint for reviews svc called reviews-svc-waypoint.

Ref to https://kmesh.net/en/docs/userguide/try_waypoint/ for how to deploy waypoint.

Access bookinfo, the result is as follow:

root@kurator-linux-0002:~# kubectl exec deploy/sleep -- sh -c "curl -s http://productpage:9080/productpage | grep reviews-v.-" 
command terminated with exit code 1

The access log of ns waypoint:

[2024-08-06T07:07:05.632Z] "GET /details/0 HTTP/1.1" 200 - via_upstream - "-" 0 178 1 1 "-" "curl/8.9.1" "36e99792-52f6-43be-96f7-6673879a85fe" "details:9080" "10.244.0.93:9080" inbound-vip|9080|http|details.default.svc.cluster.local 10.244.0.103:45656 10.96.254.42:9080 envoy://internal_client_address/ - default
[2024-08-06T07:07:05.628Z] "GET /productpage HTTP/1.1" 200 - via_upstream - "-" 0 3889 15 14 "-" "curl/8.9.1" "36e99792-52f6-43be-96f7-6673879a85fe" "productpage:9080" "10.244.0.92:9080" inbound-vip|9080|http|productpage.default.svc.cluster.local 10.244.0.103:54996 10.96.10.221:9080 envoy://internal_client_address/ - default

The waypoint of reviews svc doesn't print any access log.

What you expected to happen:

Regardless of how waypoints are deployed, we must be able to access normally

How to reproduce it (as minimally and precisely as possible):

As above.

Anything else we need to know?:

Environment:

  • Kmesh version:
  • Others:

Metadata

Metadata

Assignees

No one assigned

    Labels

    kind/bugSomething isn't working

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions