cgilling
cgilling
When using a context with a namespace that is not `default`, pod completion is for default namespace
I looked into the code a bit and it seems like the issue is that the completer always uses the default namespace when looking pods (see [here](https://github.com/c-bata/kube-prompt/blob/6f52ee1f1635ff2ebc74c85f212767e77ed7c9ba/kube/resource.go#L177)) Where as since...
When using a context with a namespace that is not `default`, pod completion is for default namespace
great thanks
@RangelReale sorry for the delayed response. My assumption is that it would be both. My only experience is with the prometheusremotewrite metrics stuff which has a way to turn off...
Thanks for bringing that to my attention, I'll have to take a look at the PR. My understanding is that the ADOT layer is a packaging of the otel collector...
@adcharre for imlementing this. I'm just getting back into investigating performance now and looked at you PR and it does indeed look like what I was hoping for as a...
I just want to add my voice to wanting to get this processor added, seems like it shouldn't be a lot of work to add it since its already a...
I would like to echo that I think the benefit of being able to force `veneurglobalonly` for all calculated metrics associated with timing and histogram would be quite useful. The...
I just wanted to comment that I just tested this with dbt-redshift version 1.9 and it does indeed work