Can we do better with per namespace deployments of metric beats?
I would wonder if there is a way to mount the secrets, and then every some unit time restart the metric beat pod (maybe doing a rolling upgrade so there is no loss of coverage, though at least in my case a gap of a few seconds is acceptable).
If there are multiple namespaces then you would need multiple metric beats pods, but you would probably want different kibana boards in any case for that.
What I'm not clear on is how to do the service discovery. I see that the hint autodiscovery can get the secrets, but if I don't want to actually put the secret in the annotation, is there a way to put the secret key and value name in the annotation, and then
have metricbeat get the secret from k8s? I don't think there is a technical problem, but I also don't know that it's supported.
Thanks for the warm welcome