Kmesh

The existing Kmesh website theme struggled to meet existing development needs. Therefore, there is a need to redesign the Kmesh website and replace the theme to make it easier for developers to add documentation. Development instructions for the website are also provided. Expected Outcome: 1. The website has more readable documentation, covering user cases, developer courses, etc. 2. Docs about how to develop website.

Currently, Kmesh metrics are only reported when a TCP connection is closed. In the case of long connections, it is not possible to know the status before the connection is closed. Therefore, we hope to add the capability to periodically report metrics for long connections. Expected Outcome: 1. proposal 2. code 3. user guide

Kmesh employs eBPF for load balancing. However, at present it only supports short-lived connections and offers a limited range of load balancing algorithms. Consequently, we aim to support a broader range of load balancing capabilities. - Expected Outcome: - 1.Load balancing with load-dependent connections via eBPF. - 2.Support as many load balancing algorithms as possible - 2.1 Sticky Round Robin - 2.2 Weighted Round Robin - 3.Userguide and Proposal - 4.Unit Test and E2E test

Kmesh, as a high-performance service mesh data plane, is now only supported for use in a single cluster. However, now that multi-cluster support for istiod has been realized, we are able to move forward with the multi-cluster adaptation of Kmesh to support the use of Kmesh in multi-cluster environments. Adaptation to the current multi-cluster production environment with LLM and large data. - Expected Outcome: - 1.Code for implementing the Kmesh multi-cluster feature - 1.1. Adapting to the Istio Multi-Cluster Function API - 1.2. Traffic Management in multi-cluster scenarios - 1.3. Use IPsec to ensure the security of node communication. - 2.userguide doc - 2.1. proposal - 2.2. userguide - 3.e2e test - 3.1. Unit Test of Feature Function - 3.2. E2E test code

<p>[Headlamp](https://headlamp.dev) is an open-source, extensible Kubernetes web UI offering easy cluster management, multi-cluster support, RBAC, and a plugin system for adding custom functionality. Users who work with Kmesh today have to switch back and forth between Headlamp (for general Kubernetes resource management) and CLI tools / `kubectl` (for Kmesh-specific inspection), which creates a fragmented workflow and a poor user experience. There is currently no simple visual way to view Kmesh resources, inspect waypoints and related components, understand overall mesh status, or troubleshoot issues quickly from within an interface users already use. This project proposes building a Headlamp plugin for Kmesh that brings Kmesh resources directly into the Headlamp UI, providing lightweight visibility of Kmesh resources alongside other Kubernetes resources. The full-featured Kmesh dashboard remains the place for advanced operations; the Headlamp plugin focuses on reducing context switching and improving ease of use for day-to-day workflows.</p><p><br></p><p><br></p><p>Expected Outcome:</p><p><br></p><p>&nbsp;- A Headlamp plugin (TypeScript/React) that registers Kmesh CRDs and surfaces them as first-class resources in the Headlamp UI.</p><p><br></p><p>&nbsp;- List and detail views for core Kmesh resources (e.g., waypoints and eBPF map)</p><p><br></p><p>&nbsp;- Visual indicators of mesh status: per-resource health, readiness, and recent Events; cluster-level summary of Kmesh components.</p><p><br></p><p>&nbsp;- Inspection helpers: pretty-printed YAML, related-pod views, and quick links to associated workloads/services.</p><p><br></p><p>&nbsp;- Documentation (README, screenshots, install guide) and a published plugin (Helm/manifest or Headlamp plugin registry entry).</p><p><br></p><p>&nbsp;- Unit/component tests for the plugin and an end-to-end smoke test against a kind/minikube cluster running Kmesh.</p>