lorelei-rupp-imprivata

> Sorry, I thought I actually answered here already 😄 @jamiepedwards yeah it makes sense to split the check, I also thought about splitting it in the mentioned connection check...

I agree with the suggested solution. The check shouldn't be doing the extra deep check. Instead of a seperate check on the header policy, so it can reside in another...

We are hitting this too, in our case the create_before_destroy does not work because the existing waf is just being updated not replaced To workaround this we had to do...

This is fixed if you use ``` receivers: awscontainerinsightreceiver: add_full_pod_name_metric_label: true prefer_full_pod_name: true``` As well as the FullPodName in your dimentions instead of PodName on the metrics exporter section

another thing to add here, this works well for an argocd that is managing a cluster its deployed within. I am not sure of the solution when Argocd is managing...

We really would love to get this fix here, as we really want argo to manage and track resources created by operators, such as the gpu operator by nvidia, it...

@daniel-butler-irl interesting, I did not get that impression, but I will test that theory out if I get some time today

@humivo @bryan-aguilar so I just rolled this out but im not seeing this actually work I put this in my configmap, added the log_retention item ``` apiVersion: v1 data: collector.yaml:...

This seems like an unfortunate issue that AMG has and AMG should solve it. While they do call it out its expected to me that is just a known bug....

> Ok Thanks for clarifying. Hope this will come asap being a vary nasty bug that can bring users to change product. In the meantime, have you any advise on...