Current status of sharding functionality

[rashmichandrashekar]

Hi, We are planning to take dependency of sharding capabilities of kube-state-metrics and have a few questions before we do so.
What is the current status of sharding functionality? Is it still in preview or is it ready for production purposes?
I see note that says "Sharding should be used carefully and additional monitoring should be set up in order to ensure that sharding is set up and functioning as expected (eg. instances for each shard out of the total shards are configured)." Is this for the considerations of network traffic and resource consumption only? Or does it mean that it can have potential issues and should be carefully monitored?

Also, I see To optimize this further, the Kubernetes API would need to support sharded list/watch capabilities. In the optimal case, memory consumption for each shard will be 1/n compared to an unsharded setup - Currently this doesn't exist. Is there any work happening in this stream to help with kube-state-metrics sharding?

Thanks in advance!

[k8s-ci-robot]

This issue is currently awaiting triage.

If kube-state-metrics contributors determine this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[CatherineF-dev]

How many nodes and pods do you have?

[rashmichandrashekar]

We have our largest customer at ~2200 nodes and roughly 65k pods. But wont that also depend on that other resources that we collecting metrics for?

[rashmichandrashekar]

Also, a followup on the sharding configuration itself. Is the only supported scenario to use horizontal sharding via automated sharding? Is running 2 deployment instances with shard=0 and shard=1 with total-shards=2 explicitly a supported scenario?

[rashmichandrashekar]

@CatherineF-dev - Gentle Ping :) Could you pls get the questions answered?

[richabanker]

/assign @CatherineF-dev
Catherine since you have already had a look at this, could you follow up on this please? Thanks!

[rashmichandrashekar]

@richabanker - Is there a sig meeting happening currently that i can join? The invite on the github repo doesnt seem to work. is there an updated one?

[richabanker]

ah missed this, yes the triage meeting happened today

The invite on the github repo doesnt seem to work.

oh are you referring to the invite here ?

[richabanker]

Ah yeah its pointing to the wrong invite. The Agenda doc though has the right one.

Updating the one mentioned on https://github.com/kubernetes/community/tree/master/sig-instrumentation