HTTP requests fail after applying waypoint to default namespace with kmeshctl

[Flying-Tom]

What happened:

After configuring a waypoint for the default namespace via the command kmeshctl waypoint apply -n default --enroll-namespace, execution of the command kubectl exec sleep-xxxx -c sleep -- curl -IsS "http://httpbin:8000/status/200" fails. The issue persists even when replacing the httpbin service name with its corresponding pod IP address.

What you expected to happen:

The command kubectl exec sleep-xxxx -c sleep -- curl -IsS "http://httpbin:8000/status/200" should execute successfully and return the expected HTTP 200 status code response.

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

1. Deploy the required workloads (sleep and httpbin) in the default namespace.
2. Run kmeshctl waypoint apply -n default --enroll-namespace to set up the waypoint for the default namespace.
3. Execute kubectl exec sleep-xxxx -c sleep -- curl -IsS "http://httpbin:8000/status/200" and verify the failure.

Anything else we need to know?:

Environment:

• Kmesh version: v1.0.0
• Kmesh mode(kmesh has Kernel-Native Mode and Dual-Engine Mode): Dual-Engine Mode
• Istio version: 1.26.0 for client, 1.27.1 for control plane
• Kernel version: 5.15.0
• Others:

[Flying-Tom]

@YaoZengzeng

[YaoZengzeng]

@Flying-Tom can you paste the log of Kmesh daemon and waypoint?

[LiZhenCheng9527]

Can you provide your istiod version?

[Flying-Tom]

Can you provide your istiod version?

istioctl version (remote):
client version: 1.26.0
control plane version: 1.27.1
data plane version:  (3 proxies), 1.24.0 (1 proxies)

istiod deployment image:
docker.io/istio/pilot:1.27.1

[LiZhenCheng9527]

The version you installed is not maintained by Kmesh. This prevents workload.Getwaypoint() from retrieving waypoint information.
Then Waypoint information cannot be included in the backend_value. Caused the access to fail.

[hzxuzhonghu]

https://kmesh.net/docs/setup/quick-start#prerequisites It aligns with this doc

[Flying-Tom]

kmesh.net/docs/setup/quick-start#prerequisites It aligns with this doc

The prerequisites currently lack an upper version limit for Istiod, and this problem occurs when the waypoint feature is in use. For reference, a related PR has been submitted: kmesh-net/website#239

[hzxuzhonghu]

You mean istio > 1.25 is not compatible with kmesh?

[Flying-Tom]

You mean istio > 1.25 is not compatible with kmesh?

I think so. Currently, Kmesh primarily maintains the main versions ranging from 1.23 to 1.25. For Istio versions higher than 1.25, there is no corresponding E2E testing support yet.

[LiZhenCheng9527]

This issue has been resolved.
/close

[kmesh-bot]

@LiZhenCheng9527: Closing this issue.

In response to this:

This issue has been resolved.
/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.