Tiger Xu / Zhonghu Xu
Tiger Xu / Zhonghu Xu
**What would you like to be added**: This is to improve test coverage for features, we should test each feature in black box way. I am not sure whether github...
**What type of PR is this?** **What this PR does / why we need it**: **Which issue(s) this PR fixes**: Fixes # **Special notes for your reviewer**: **Does this PR...
**What would you like to be added**: Currently we only support namespace level by labeling `istio.io/dataplane-mode: Kmesh`. In some case, people want to explictly exclude some workload or only include...
**What would you like to be added**: 1. Currently we support only src ip, port authorizationpolicy. Some more dimesions should be supported. ``` type Match struct { state protoimpl.MessageState sizeCache...
**What would you like to be added**: We should not require workloads to be restarted after kmesh restarted. So we may need to auto reload bpf maps after kmesh restarted,...
**What would you like to be added**: From istio 1.22, it has supported waypoint capture for service, pod, besides namespace, https://github.com/istio/istio/issues/49032 Basically it inroduced a new annotation ` istio.io/use-waypoint: [{namespace}/]{gateway-name}`...
**What would you like to be added**: Currentlt kmesh has no metrics, accesslogs or traces at all. All of these are demanding features for a mesh. I would propose we...
**What would you like to be added**: For east-west service communication, we should encrypt the traffic to implement zero-trust network. As to ingress traffic through ingressgateway, we should do similar,...
**What would you like to be added**: 1. Add some debug level logs to indicate ebpf prog is working 2. Fix unexpected log on bpf_map_delete_elem
we should support log level setting in 1. kmesh daemon both when startup and dynamiclly 2. bpf prog log level setting, @bitcoffeeiux can you shed some light on it