With the help of the service topology map, users can fully understand the dependencies and communication status between various services in the cluster, making it easier to monitor and diagnose network conditions. Users can also identify potential performance bottlenecks and failure points, optimize and troubleshoot, and improve the reliability and performance of the entire system.
In version v1.0.0, Kmesh's Kernel-Native mode also provides the ability to restart traffic without interruption. It can load eBPF map and Prog gracefully after restart, and does not need to re-register services after restart. This achieves the goal of restarting Kmesh in full mode without interrupting traffic and affecting services.
As in Dual-Engine mode, eBPF Prog and map are pinned to the kernel kazakhstan phone number data directory to decouple them from kmesh-daemon, ensuring that eBPF map and Prog can manage traffic even when Kmesh is shut down, ensuring that services are not interrupted during Kmesh restart.
If there is a configuration update during the time when Kmesh restarts, Kmesh will also obtain the latest configuration from istiod after restarting to ensure that the information is synchronized as soon as possible after the restart.
Compared with the situation where traditional Service Mesh interrupts service traffic during the restart process, Kmesh's design avoids the impact on business traffic during the restart period, ensures the continuity and stability of the service, provides a more reliable and highly available system, reduces the risk of service interruption, and improves user experience. In addition, in the subsequent plan, Kmesh will support non-interruption upgrades to ensure that business traffic will not be interrupted when Kmesh is upgraded, solving the problem that users want to use new mesh functions but dare not upgrade the mesh.