-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support to use vegeta client with HTTPS #14255
Conversation
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: nak3 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:
Approvers can indicate their approval by writing |
/test foo |
@nak3: The specified target(s) for
The following commands are available to trigger optional jobs:
Use
In response to this:
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. |
/test https |
Codecov ReportPatch coverage has no change and project coverage change:
Additional details and impacted files@@ Coverage Diff @@
## main #14255 +/- ##
==========================================
+ Coverage 86.25% 86.26% +0.01%
==========================================
Files 199 199
Lines 14811 14811
==========================================
+ Hits 12775 12777 +2
+ Misses 1734 1732 -2
Partials 302 302 ☔ View full report in Codecov by Sentry. |
e2e test supports `--https` option but vegeta client always uses "HTTP". This patch supports https wit so vegeta uses TLS client.
099d3e7
to
ad447b4
Compare
/retest Infra issue |
/lgtm |
e2e test supports
--https
option but vegeta client always uses "HTTP".This patch supports https wit so vegeta uses TLS client.
Release Note