-
Notifications
You must be signed in to change notification settings - Fork 295
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
🌱 test: use a daemonset and kubectl exec to provide images to remote clusters #2955
🌱 test: use a daemonset and kubectl exec to provide images to remote clusters #2955
Conversation
/test help |
@chrischdi: 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 pull-cluster-api-provider-vsphere-e2e-govmomi-main |
1 similar comment
/test pull-cluster-api-provider-vsphere-e2e-govmomi-main |
73b6281
to
65d0320
Compare
/test pull-cluster-api-provider-vsphere-e2e-govmomi-main |
3a4d88c
to
e41e5f2
Compare
/test pull-cluster-api-provider-vsphere-e2e-govmomi-main |
e41e5f2
to
9820cfb
Compare
/test pull-cluster-api-provider-vsphere-e2e-govmomi-main |
9820cfb
to
2cdbd39
Compare
/test pull-cluster-api-provider-vsphere-e2e-govmomi-main |
/test pull-cluster-api-provider-vsphere-e2e-govmomi-main |
/test pull-cluster-api-provider-vsphere-e2e-supervisor-blocking-main |
2cdbd39
to
0610679
Compare
/test pull-cluster-api-provider-vsphere-e2e-govmomi-main |
1 similar comment
/test pull-cluster-api-provider-vsphere-e2e-govmomi-main |
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.
Really really nice!!
/cherry-pick release-1.10 |
@chrischdi: once the present PR merges, I will cherry-pick it on top of release-1.10 in a new PR and assign it to you. 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-sigs/prow repository. |
/cherry-pick release-1.9 |
@chrischdi: once the present PR merges, I will cherry-pick it on top of release-1.9 in a new PR and assign it to you. 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-sigs/prow repository. |
/cherry-pick release-1.8 |
@chrischdi: once the present PR merges, I will cherry-pick it on top of release-1.8 in a new PR and assign it to you. 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-sigs/prow repository. |
/cherry-pick release-1.7 |
@chrischdi: once the present PR merges, I will cherry-pick it on top of release-1.7 in a new PR and assign it to you. 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-sigs/prow repository. |
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
/approve
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: fabriziopandini 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 |
/retest |
@chrischdi: #2955 failed to apply on top of branch "release-1.7":
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-sigs/prow repository. |
@chrischdi: #2955 failed to apply on top of branch "release-1.10":
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-sigs/prow repository. |
@chrischdi: #2955 failed to apply on top of branch "release-1.9":
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-sigs/prow repository. |
@chrischdi: #2955 failed to apply on top of branch "release-1.8":
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-sigs/prow repository. |
…clusters (kubernetes-sigs#2955) * test: use a daemonset and kubectl exec to provide images to remote clusters * review fixes * review fixes * log io.Copy error * fix typo
…clusters (kubernetes-sigs#2955) * test: use a daemonset and kubectl exec to provide images to remote clusters * review fixes * review fixes * log io.Copy error * fix typo
No need to cherry-pick it back to v1.8 or v1.7, because we don't have clusterctl upgrade tests there 😄 🍺 |
…clusters (kubernetes-sigs#2955) * test: use a daemonset and kubectl exec to provide images to remote clusters * review fixes * review fixes * log io.Copy error * fix typo
…clusters (kubernetes-sigs#2955) * test: use a daemonset and kubectl exec to provide images to remote clusters * review fixes * review fixes * log io.Copy error * fix typo
Great news! :) |
…clusters (kubernetes-sigs#2955) * test: use a daemonset and kubectl exec to provide images to remote clusters * review fixes * review fixes * log io.Copy error * fix typo
…clusters (kubernetes-sigs#2955) * test: use a daemonset and kubectl exec to provide images to remote clusters * review fixes * review fixes * log io.Copy error * fix typo
What this PR does / why we need it:
Removes pushing the images to gcloud and instead uses a daemonset and streams the image tarball via kubectl exec.
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 #