/assign tariq1890

Signed the CLA

@jpenekusu can you explain a bit more what kind of metrics you are looking for, we already have pod resource metrics in both Kubernetes as well as in kube-state-metrics.

It seems that go 1.16 introduced some changes that made our modules test fail, see https://github.com/kubernetes/kube-state-metrics/pull/1397. That PR as a workaround pinned to 1.15 version. We should pin to go 1.16+ and fix any issues that made that job fail.

**Result: **

Our CI uses go 1.16+.

Thank you @lou-lan! 🎉

<!-- Please only use this template for submitting feature requests -->

What would you like to be added:

In environments where only namespaced resources are monitored via kube-state-metrics it would be useful to have an optional parameter in helm chart to configure whether a single or multiple Deployments/StatefulSets of ksm is deployed. When enabled this can work as a per-namespace sharding as individual ksm deployments can one separate namespaces.

Why is this needed: Sharding kube-state-metrics metrics collection.

Describe the solution you'd like Add a new parameter in helm chart

# When enabled,. namespace sharding creates one Deployment/Stateful for each scraped namespace 
# namespaceSharding:
#  enable: true

Additional context

<!-- Thanks for sending a pull request! Here are some tips for you:

1. If this is your first time, read our contributor guidelines https://git.k8s.io/community/contributors/guide/pull-requests.md#the-pull-request-submit-process and developer guide https://git.k8s.io/community/contributors/devel/development.md#development-guide
2. If you want faster PR reviews, read how: https://git.k8s.io/community/contributors/guide/pull-requests.md#best-practices-for-faster-reviews
3. Follow the instructions for writing a release note: https://git.k8s.io/community/contributors/guide/pull-requests.md#write-release-notes-if-needed
4. If the PR is unfinished, see how to mark it: https://git.k8s.io/community/contributors/guide/pull-requests.md#marking-unfinished-pull-requests -->

What this PR does / why we need it:

This PR bump go version in CI to 1.16+.

@brancz @lilic

Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged): Ref: #1398

/hold cancel

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: <a href="https://github.com/kubernetes/kube-state-metrics/pull/1399#issuecomment-788012450" title="LGTM">lilic</a>, <a href="https://github.com/kubernetes/kube-state-metrics/pull/1399#" title="Author self-approved">lou-lan</a>

The full list of commands accepted by this bot can be found here.

The pull request process is described here

<details > Needs approval from an approver in each of these files:

• OWNERS [lilic]

Approvers can indicate their approval by writing /approve in a comment Approvers can cancel approval by writing /approve cancel in a comment </details> <!-- META={"approvers":[]} -->

/lgtm

Thank you!!

/hold @brancz feel free to release the hold 🎉

@andreihagiescu-db: PR needs rebase.

<details>

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/test-infra repository. </details>

Keywords which can automatically close issues and at(@) or hashtag(#) mentions are not allowed in commit messages.

The list of commits with invalid commit messages:

• ab1143e [stable/kube-state-metrics] add pod affinity (#12819)
• 21b54d2 [stable/kube-state-metrics] Version bump to 1.9.5 (#20915)

<details>

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/test-infra repository. I understand the commands that are listed here. </details>

I think this is the most rigorous, I changed it to 1.16+.

Any updates?

Already merged into rc2 branch

Sorry one more thing I missed, since we no require 1.16 go version we should setup our CI to be go 1.16 onwards for all jobs in this file.

Any updates?

Yes I thought so as well, do you mind doing that? Thank you! I have updated.

I have another question. Should I commit to master or release-2.0 ?

We want it in release-2.0 first and we will port to master when rc happens this week.

The version of go directive should be updated to 1.16

Yes I thought so as well, do you mind doing that? Thank you!

Issues go stale after 90d of inactivity. Mark the issue as fresh with /remove-lifecycle stale. Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale

@lilic I have changed as per the review comments, the main intention of this PR is the functionality of the package docscollector, It is required to fetch all the resources but currently have took one example as the resource: configMapMetricFamilies.

Issues go stale after 90d of inactivity. Mark the issue as fresh with /remove-lifecycle stale. Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale

/remove-lifecycle stale

I will pick up this again with the newly added info

Issues go stale after 90d of inactivity. Mark the issue as fresh with /remove-lifecycle stale. Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale