Add performance test

[jwcesign]

Fix #151

[knative-prow]

Hi @jwcesign. Thanks for your PR.

I'm waiting for a knative-sandbox 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/test-infra repository.

[codecov]

Codecov Report

Merging #156 (37a14f7) into main (8451375) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main     #156   +/-   ##
=======================================
  Coverage   67.35%   67.35%           
=======================================
  Files           5        5           
  Lines         193      193           
=======================================
  Hits          130      130           
  Misses         44       44           
  Partials       19       19           

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

[jwcesign]

/test pull-knative-sandbox-container-freezer-build-tests

[knative-prow]

@jwcesign: Cannot trigger testing until a trusted user reviews the PR and leaves an /ok-to-test message.

In response to this:

/test pull-knative-sandbox-container-freezer-build-tests

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.

[jwcesign]

cc @psschwei give one /ok-to-test,I will do tests here

[jwcesign]

So for the useage like:

/test pull-knative-sandbox-container-freezer-performance-tests-hey

First, I should set here test-infra

Than add a shell file in this PR.
finally trigger it with /test pull-knative-sandbox-container-freezer-performance-tests-hey ?

[knative-prow]

@jwcesign: Cannot trigger testing until a trusted user reviews the PR and leaves an /ok-to-test message.

In response to this:

So for the useage like:

/test pull-knative-sandbox-container-freezer-performance-tests-hey

First, I should set for config

Than I can add a test file and trigger it with /test pull-knative-sandbox-container-freezer-performance-tests-hey ?

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.

[psschwei]

/ok-to-test

[jwcesign]

/test pull-knative-sandbox-container-freezer-build-tests

[knative-prow]

@jwcesign: The specified target(s) for /test were not found.
The following commands are available to trigger required jobs:

• /test build-tests_container-freezer_main
• /test integration-tests_container-freezer_main
• /test unit-tests_container-freezer_main

Use /test all to run all jobs.

In response to this:

/test pull-knative-sandbox-container-freezer-build-tests

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.

[jwcesign]

cc @nader-ziada @psschwei , when you are available, please check it. It works on my local cluster when comment initialize --min-nodes=2 --max-nodes=2 --cluster-version=1.23 "$@"

[jwcesign]

copy from serving repo

[psschwei]

Let's keep the dates in both scripts as 2022 since that's when they were added to this repo

[jwcesign]

fixed

[jwcesign]

copy from serving repo

[psschwei]

Couple nits:

• when I pulled the PR, none of the scripts were marked executable, I think they'll need a chmod +x in order to run via prow
• test currently requires istio in order to generate results, as get_gateway_ip() checks the istio namespace
• there's a lot of bits in the copied over tests scripts that we aren't using and could probably be cut

[jwcesign]

test currently requires istio in order to generate results, as get_gateway_ip() checks the istio namespace.

I use setup_ingress_env_vars to set the gateway env then use it directly(all the logic is from serving repo)

[psschwei]

/lgtm
/approve

We might want to add a README for the performance test with a note on how to use an alternative ingress, but can do that in a separate PR.

Thanks for adding this!

[knative-prow]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: jwcesign, psschwei

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

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [psschwei]

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