feat: Add performance tests for custom-resource-state-metrics

[Rishab87]

What type of PR is this?

/kind feature

What this PR does / why we need it:

This PR introduces performance tests for the custom-resource-state-metrics feature, as requested in the issue.

It adds two parallel test scenarios to compare the performance of KSM's native namespace collector against the new custom-resource-state collector for the same workload (500 namespaces with 5 labels each). This allows for a direct performance comparison between the two modes.

Which issue(s) this PR fixes:

Fixes kubernetes/kube-state-metrics#1902

Special notes for your reviewer:

This is my first time ever contributing to k8s, I'm not able to see performance metrics in logs, the tests pass, would really appreciate reviews & some help on this.

[linux-foundation-easycla]

The committers listed above are authorized under a signed CLA.

• ✅ login: Rishab87 / name: Rishab Kumar Jha (7074194, bcf1e58, 20c5341)

[k8s-ci-robot]

Welcome @Rishab87!

It looks like this is your first PR to kubernetes/perf-tests 🎉. Please refer to our pull request process documentation to help your PR have a smooth ride to approval.

You will be prompted by a bot to use commands during the review process. Do not be afraid to follow the prompts! It is okay to experiment. Here is the bot commands documentation.

You can also check if kubernetes/perf-tests has its own contribution guidelines.

You may want to refer to our testing guide if you run into trouble with your tests not passing.

If you are having difficulty getting your pull request seen, please follow the recommended escalation practices. Also, for tips and tricks in the contribution process you may want to read the Kubernetes contributor cheat sheet. We want to make sure your contribution gets all the attention it needs!

Thank you, and welcome to Kubernetes. 😃

[k8s-ci-robot]

Hi @Rishab87. Thanks for your PR.

I'm waiting for a kubernetes member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

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.

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: Rishab87
Once this PR has been reviewed and has the lgtm label, please assign mborsz for approval. For more information see the Code Review Process.

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

Needs approval from an approver in each of these files:

• clusterloader2/OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[rexagod]

@Rishab87 Hello, thank you for this! Since this is a draft, I'm assuming there's some pending changes left here?

[Rishab87]

@rexagod yes, I'm not able to see performance metrics in logs, I need to fix that, I will mark it ready for review once it is fixed. Would really appreciate any help on this otherwise I'll try to get it done by next week.

[Rishab87]

@mborsz @wojtek-t , Im still stuck at this do you have any idea? I'm able to run the tests with this command:

./clusterloader2/clusterloader   --testconfig=./clusterloader2/testing/prometheus/custom-resource-state-metrics.yaml   --provider=kind   --kubeconfig=$HOME/.kube/config   --v=2

The tests pass:

I0813 20:28:28.366733  180393 clusterloader.go:253] --------------------------------------------------------------------------------
I0813 20:28:28.366746  180393 clusterloader.go:254] Test Finished
I0813 20:28:28.366758  180393 clusterloader.go:255]   Test: ./clusterloader2/testing/prometheus/custom-resource-state-metrics.yaml
I0813 20:28:28.366770  180393 clusterloader.go:256]   Status: Success
I0813 20:28:28.366780  180393 clusterloader.go:260] --------------------------------------------------------------------------------

But I am not able to see the performance metrics it also finishes very soon to under 10 secs.