-
Notifications
You must be signed in to change notification settings - Fork 2.9k
Make ci-kubernetes-e2e-gci-gce-autoscaling build new CA image #36336
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
Conversation
|
Hi @Choraden. 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 Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. DetailsInstructions 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. |
Can you link for posterity? /ok-to-test |
|
/lgtm |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: Choraden, towca The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
This patch disables cluster autoscaler deployment by kubetest2 gce. Instead, Cluster Autoscaler run script was extended to build and deploy new CA image on every run.
59320d4 to
0eda526
Compare
|
/lgtm |
|
/unhold |
|
@Choraden: Updated the
DetailsIn 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-sigs/prow repository. |
This patch disables cluster autoscaler deployment by kubetest2 gce. Instead, Cluster Autoscaler run script was extended to build and deploy new CA image on every run.