It has a proposed solution in : #3408
It seems very reasonable ask.

So, I am adding triage accepted.

There are still some discussions happening on this thread kubernetes/kube-state-metrics#2065, should we wait until the consensus is made ?

Boiling down that thread, the overall ask is to have a de-facto way of pluralizing that helps keep the resource names consistent throughout the ecosystem. I believe using the same logic as apimachinery should allow us to achieve that.

/assign

Hey @mrueg @rexagod , would you provide some cases/code snippets that come with such an attempt to make the plural consistent? I'm trying to understand how the consistent plural system can help kubernetes clients to resolve a resourceplural from a GroupVersionKind mapping.

We've had to extract and match plurals to avoid instances where there may be discrepancies between the expected and actual plurals.

Enforcing a common "de-facto" standard through kubebuilder will solve such cases to a great extent.

Should I take this up? @Kavinjsir @varshaprasad96 @camilamacedo86

Hello @camilamacedo86 It looks like code issue. Should I work on this?
I have gone through the pr. understood somewhat maybe. I would give it a try if possibe.
If there is anything else I should know or refer to let me know.