-
Notifications
You must be signed in to change notification settings - Fork 431
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
Adding HTTP Proxy support for managed cluster #3847
Conversation
Hi @mjnovice. Thanks for your PR. I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the 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. |
/ok-to-test |
2fe0a92
to
22afe36
Compare
/retest |
22afe36
to
cfac689
Compare
/retest |
cfac689
to
8f0b37f
Compare
/retest |
/retest pull-cluster-api-provider-azure-e2e |
@Jont828: The
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 pull-cluster-api-provider-azure-e2e |
Looks like you had a failure with the VMSS e2e test, rerunning in case it's a flake. |
/assign |
283912b
to
7eb5cec
Compare
82d36e7
to
6c44b7c
Compare
@mjnovice The verify error seems to be a linting issue with the shellcheck script. |
My comment might have gotten buried into resolved comments, but I would love to hear your thoughts @mjnovice |
@Jont828 seems to be a ratelimit issue ? https://prow.k8s.io/view/gs/kubernetes-jenkins/pr-logs/pull/kubernetes-sigs_cluster-api-provider-azure/3847/pull-cluster-api-provider-azure-verify/1691920826074402816#1:build-log.txt%3A510 |
/test pull-cluster-api-provider-azure-verify |
@nawazkh have replied to your comment. 🙂 let me know your thoughts. |
Thanks for the explanation @mjnovice |
LGTM label has been added. Git tree hash: afb3af912078a859733a4270516d8b71d3d851a7
|
I've seen a Docker rate limiting issue when testing locally, but I haven't seen that in the CI jobs. If it comes up again we could open an issue. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just a quick thing, otherwise I think we're good to go!
6c44b7c
to
a13fa67
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
Nice work!
LGTM label has been added. Git tree hash: dde1e38395dd5ecbd9ee295486cab45ff9369257
|
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: CecileRobertMichon 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 |
What type of PR is this?
/kind feature
What this PR does / why we need it:
Which issue(s) this PR fixes (optional, in
fixes #<issue number>(, fixes #<issue_number>, ...)
format, will close the issue(s) when PR gets merged):Fixes #3485
Special notes for your reviewer:
TODOs:
Release note: