Pranshu Srivastava

It makes sense to acknowledge the resolution on https://github.com/kubernetes-sigs/kubebuilder/issues/3402 and not make them dependent on the "broken" pluralization logic upstream. Both of these places have procedures, albeit differing in nature,...

~~Right off the top of my mind, I'd say this happens because we `buildCustomStore` for anything defined in the CRS config.~~ If the GVK is something that KSM supports natively,...

Putting it out there that [this](https://github.com/kubernetes/kube-state-metrics/issues/2044#issuecomment-1542449829) is still the case, and the later built (custom) stores are the only ones in effect. Details #### Native Store (registered first) ![Screenshot from...

@grzesuav I'm not sure if it's possible (I'm leaning towards the contrary based on my understanding), but is it possible for KSM to expose metrics for the same native and...

I found out that `--custom-resource-state-only` can be used to only output CRS metrics, using this flag fixes this issue in case of same object in the CRS configuration and the...

@slashpai Can I take this up (if you're not working on this currently)? 🙂

@simonpasquier Applying this, I can see logs indicating the error, but not actually failing the container. ``` level=error ts=2024-05-28T04:23:03.451526556Z caller=reloader.go:308 msg="apply error" err="expand environment variables: found reference to unset environment...

ACK, in that case, I think this can be closed now.

I couldn't reproduce this with the aforementioned snippet running for a thousand times. @shaohk Are you still able to reproduce this with the latest release?

@Dentrax Just a nit, but can you add `Fixes #478` to the description so that the original issue is closed when this gets in?