k8s v1.23, the APIResponsivenessPrometheus some metrics cannot be collected compared with k8s v1.22 like "podsecuritypolicies" "podmonitors" "controllerrevisions" "csistoragecapacities csidrivers"

[DavidQuan-vmware]

What happened: For k8s v1.23, the APIResponsivenessPrometheus some metrics cannot be collected compared with k8s v1.22, the metrics which cannot be collected as bellow : "podsecuritypolicies" "podmonitors" "controllerrevisions" "csistoragecapacities csidrivers"

k8s v1.22 metrics: APIResponsivenessPrometheus_mgmt-cluster-perf_2022-06-24T05:52:17-07:00.json|grep podsecuritypolicies -A13 "Resource": "podsecuritypolicies", "Scope": "cluster", "SlowCount": "0", "Subresource": "", "Verb": "LIST" } }, { "data": { "Perc50": 550, "Perc90": 880, "Perc99": 898 }, "unit": "ms",

k8s v1.23 metrics: cat APIResponsivenessPrometheus_mgmt-cluster-perf_2022-09-21T11:19:03Z.json|grep podsecuritypolicies -A13 "Resource": "podsecuritypolicies", "Scope": "cluster", "SlowCount": "0", "Subresource": "", "Verb": "LIST" } }, { "data": { "Perc50": 0, "Perc90": 0, "Perc99": 0 }, "unit": "ms",

Thanks for checking on this.

What you expected to happen: expected the metric of "podsecuritypolicies" "podmonitors" "controllerrevisions" "csistoragecapacities csidrivers" can be collected in APIResponsivenessPrometheus json.

How to reproduce it (as minimally and precisely as possible): cd /src/k8s.io/perf-tests/clusterloader2/; ./run-e2e.sh --testconfig=./testing/load/config.yaml --report-dir=$f/artifacts --masterip=$masterip --master-internal-ip=$masterip --enable-prometheus-server=true --tear-down-prometheus-server=false --prometheus-scrape-etcd=true --prometheus-scrape-kube-proxy=false --prometheus-scrape-node-exporter=false --prometheus-scrape-kubelets=true --prometheus-manifest-path /src/k8s.io//perf-tests/clusterloader2/pkg/prometheus/manifests/ --alsologtostderr --provider vsphere 2>&1 | tee $f/out.log

Anything else we need to know?:

Environment:

• Kubernetes version (use kubectl version): kubectl version Client Version: version.Info{Major:"1", Minor:"23", GitVersion:"v1.23.8+vmware.2", GitCommit:"d625665700d901401d7504761cf473dd8adfc7b3", GitTreeState:"clean", BuildDate:"2022-07-18T23:09:26Z", GoVersion:"go1.17.11", Compiler:"gc", Platform:"linux/amd64"}
• Cloud provider or hardware configuration:
• OS (e.g: cat /etc/os-release): $ cat /etc/os-release NAME="Ubuntu" VERSION="20.04.4 LTS (Focal Fossa)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 20.04.4 LTS" VERSION_ID="20.04" HOME_URL="https://www.ubuntu.com/" SUPPORT_URL="https://help.ubuntu.com/" BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/" PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy" VERSION_CODENAME=focal UBUNTU_CODENAME=focal
• Kernel (e.g. uname -a): uname -a Linux mgmt-control-plane-48gwm 5.4.0-122-generic 138-Ubuntu SMP Wed Jun 22 15:00:31 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux
• Install tools:
• Network plugin and version (if this is a network-related bug):
• Others:

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle stale
• Mark this issue or PR as rotten with /lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Reopen this issue with /reopen
• Mark this issue as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close not-planned

[k8s-ci-robot]

@k8s-triage-robot: Closing this issue, marking it as "Not Planned".

In response to [this](https://github.com/kubernetes/perf-tests/issues/2143#issuecomment-1436284292): >The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs. > >This bot triages issues according to the following rules: >- After 90d of inactivity, `lifecycle/stale` is applied >- After 30d of inactivity since `lifecycle/stale` was applied, `lifecycle/rotten` is applied >- After 30d of inactivity since `lifecycle/rotten` was applied, the issue is closed > >You can: >- Reopen this issue with `/reopen` >- Mark this issue as fresh with `/remove-lifecycle rotten` >- Offer to help out with [Issue Triage][1] > >Please send feedback to sig-contributor-experience at [kubernetes/community](https://github.com/kubernetes/community). > >/close not-planned > >[1]: https://www.kubernetes.dev/docs/guide/issue-triage/ Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.