search

kubernetes / perf-tests

Performance tests and benchmarks
Apache License 2.0
900 stars 534 forks source link

Ability to specify image repos for those used with clusterloader2 #2704

Closed rackeric closed 1 week ago

rackeric commented 5 months ago

What would you like to be added: The ability to use custom image repos with clusterloader2, specifically the deployment used by the exec_service and images used in template yamls for the load test, like deployments and statefulsets.

Why is this needed: Some clusters may not have external Internet access to reach the upstream registry.k8s.io and gcr.io image repos, but do have access to an internal mirror hosting these images.

rackeric commented 5 months ago

I've submitted a PR of the changes I use for the "load" test manifests. https://github.com/kubernetes/perf-tests/pull/2705

rackeric commented 5 months ago

And for the exec_service image here is this change to allow it to be set with clusterloader2 CLI flag. https://github.com/kubernetes/perf-tests/pull/2706

k8s-triage-robot commented 2 months ago

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

This bot triages un-triaged issues according to the following rules:

You can:

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

/lifecycle stale

k8s-triage-robot commented 1 month ago

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

This bot triages un-triaged issues according to the following rules:

You can:

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

/lifecycle rotten

k8s-triage-robot commented 1 week ago

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:

You can:

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

/close not-planned

k8s-ci-robot commented 1 week ago

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

In response to [this](https://github.com/kubernetes/perf-tests/issues/2704#issuecomment-2453581414): >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-sigs/prow](https://github.com/kubernetes-sigs/prow/issues/new?title=Prow%20issue:) repository.