If I've deployed multiple alloy instances in the same k8s cluster, in the same namespace, but for different purposes (e.g. one for scraping metrics and one for gathering pod logs), the "Cluster config drifting" alert will always fire because it cannot tell that these alloys are not meant to have the same config.
Steps to reproduce
Deploy alloy twice in the same k8s cluster, in the same namespace with different configs.
or, use the k8s-monitoring Helm chart.
What's wrong?
If I've deployed multiple alloy instances in the same k8s cluster, in the same namespace, but for different purposes (e.g. one for scraping metrics and one for gathering pod logs), the "Cluster config drifting" alert will always fire because it cannot tell that these alloys are not meant to have the same config.
Steps to reproduce
Deploy alloy twice in the same k8s cluster, in the same namespace with different configs. or, use the k8s-monitoring Helm chart.
System information
No response
Software version
No response
Configuration
No response
Logs
No response