Pranshu Srivastava

Sorry for the delay here, I got caught up, will review before end of the day. 🙂

Hello, @venkatbvc. Thank you for the PR, however, there's some development recently that affects the areas covered by the parent issue. With the [CEL](https://github.com/kubernetes/kube-state-metrics/issues/1978) and [CRD](https://github.com/kubernetes/kube-state-metrics/issues/1948) changes planned for the...

/hold Until aforementioned factors clear up.

I feel changes that address readability concerns should ideally be acted upon only if the linter finds out there's something wrong with the current way of implementing the targeted behaviors....

@mrueg @CatherineF-dev How about allowing folks to switch between YAML and JSON? We can add more decoders as well in the future. Changing the unmarshalling behavior for specific flags will...

So, are we sunsetting the older model?

Also, there was a [thread](https://kubernetes.slack.com/archives/C04C0PBR126/p1683557765323729) regarding separating the CRS featureset into its own repository (the "non-turing" solution here being CEL-like languages, that do not offer an exhaustive way of defining...

Will this mean that KSM's config capabilities will be restricted to what the underlying solution (#1978) has to offer?

@dgrisonnet I'm assuming going forward with the newer model will mean we'll deprecate the older one. So, with that in mind, are PRs such as this and others like: #2067,...

I couldn't agree more. The current CRS featureset, in addition to being complex and hardly maintainable for developers, doesn't have a clear, semantical, or easy-to-understand UX at the moment. Off...