Detailed Description: The log collector currently used in the project only supports the Sidecar deployment mode, which to some extent increases resource consumption. To improve the utilization rate of resources, it is suggested that the development team consider supporting the DaemonSet deployment method.
The DaemonSet mode can uniformly deploy the log collector across the entire Kubernetes cluster, reducing redundancy and lowering resource occupancy. Additionally, if possible, it is suggested to open source an Operator that supports the DaemonSet deployment method, so that the community and users can customize and extend it.
Expected Outcome:
Support for the log collector using the DaemonSet deployment method.
Open sourcing an Operator for the log collector based on the DaemonSet deployment method.
we are committed to supporting this feature in the future and plan to open-source an operator that facilitates the DaemonSet deployment method. This initiative is firmly on our roadmap.
Detailed Description: The log collector currently used in the project only supports the Sidecar deployment mode, which to some extent increases resource consumption. To improve the utilization rate of resources, it is suggested that the development team consider supporting the DaemonSet deployment method. The DaemonSet mode can uniformly deploy the log collector across the entire Kubernetes cluster, reducing redundancy and lowering resource occupancy. Additionally, if possible, it is suggested to open source an Operator that supports the DaemonSet deployment method, so that the community and users can customize and extend it. Expected Outcome: Support for the log collector using the DaemonSet deployment method. Open sourcing an Operator for the log collector based on the DaemonSet deployment method.