Graeme Coupar

Yeah, that seems reasonable. I suppose the only case where it'd make a difference is someone might mis-use an object proxy in an `async for` and get a slightly different...

1. Sounds sensible. Guess this would also make it less likely for existing pods to mess up tests. 2. `obmarg/health-proxy` is only 8MB, but if `alpine` itself is smaller then...

Re: 1. - Would it make sense to create a unique namespace for each tests (using a uuid as the name or something). That way integration tests can continue to...

Hi @michaeljguarino - I'm sure there are a ton of outdated resources, think I last updated the swagger specs for k8s 1.11 4 years ago. It's mostly just a case...

I've made a test branch for this here: https://github.com/obmarg/kazan/tree/feature/with_name Wondering if it'd make sense to generate `Model.with_name` functions for each model that could have a name. For example, I might...

Hello again @lswith - is there a specific use case that you've got where a decoded map isn't good enough? I guess the main problem with errors from k8s is...

Looking into this a tiny bit more, it seems like the StatusError contains a metaStatus, which is actually in the kube specs, and the [kazan struct is here](https://hexdocs.pm/kazan/0.9.0/Kazan.Models.Apimachinery.Meta.V1.Status.html) so it...

Hi @MonadicT - sorry for the delay getting back to you about this, the past month has been very busy at work and I've not had much spare time to...

This is an interesting idea, not one I'd considered. Not sure where I stand: is there a reason to do this in Kazan vs. implementing this in your app?

Handled in #571