Karl Stoney

Hey, Sorry for the delay in reviewing this, had a busy few days. Firstly, thanks a lot for the contribution, I think the custom http checks is a great addition....

Interesting, if you share your branch with me I can try and take a look tomorrow. You might not need root, just a certain netcap

OK so switching to `inline_bytes` and `base64` encoding the value "fixed" it. I was going back and forth between bytes and string y'day trying to get something working so i'm...

Literally just sat in the office talking about our dilemma of wanting to capture all errors, but sample others. But we can't sample everything, as it's too much data.

Error wouldn’t work at a trace level in a microservice architecture as the spans before your error app will have already been reported to jäger based on their sample rate

Hey, So we will experience them every day. Typically we do a lot of large data processing between 4am and 7am which is when we see these spikes. You can...

> Having an extra label just as performance optimization also does not make sense It does when you're dealing with 1000's of resources and kube-janitor is only applicable to a...

>The one caveat to the approach @sryabkov mentions, is non-namespaced resources in the helm release (ex: ClusterRoles) will not get deleted by deleting the namespace, not a huge problem but...

It seems like `pump` isn't passing through the `error`, if you add: ``` async getWatchObjectStream (options) { console.log('getting watch stream') const jsonStream = new JSONStream() const stream = this.http(Object.assign({ stream:...

> I fixed my issue by running a kubectl command before using my kubeconfig with this package. This is required for some reason because the access-token isn't populated within the...