Eirik A

> It feels like it sort of breaks that contract of safety that Rust usually offers. yeah, for sure this is awkward. We could maybe have a `Namespace` newtype somewhere...

> motivation to keep that optional on namespaced resources well, it's really just apiserver bugs you are catering for. you can unwrap, or you can propagate the error to whatever...

One thing I think could help users onboard faster by managing less configuration would be the ability to deep-merge parts of the user configuration on top of the presets. Particularly...

Yeah, something like this would be good to provide for at least the created `Service` and `Deployment` resource. The [recommended kubernetes labels](https://kubernetes.io/docs/concepts/overview/working-with-objects/common-labels/) are difficult to use as native flagger `selectorLabels`...

Thanks @aryan9600 that works great for the main `Deployment` object created. It doesn't seem to get added to the created `Sevice` objects though.

Ah, perfect. That should do it. Thank you! EDIT: yep, this sorted everything on my end.

same issue for me. was able to recover it by killing the app and wiping the savestate: ```sh pkill SpaceId cd ~/Library rm -rf Saved\ Application\ State/com.dshnkao.SpaceId.savedState/ ```

Have updated the issue a bit. Tried to clarify that this is not just a grafana display issue (though it is worse in grafana), but about producing a continuous SLI...

Ah, good to see it is possible. I was hoping that this type of thing could perhaps be defaulted within `sloth` though, so that not every user would have to...

This is almost certainly down to how musl does dns and not something we can solve here. You are putting a musl built static binary inside of a rust container...