capi: using released artifacts #260
Conversation
Signed-off-by: Carlos Panato <ctadeu@gmail.com>
k8s-ci-robot
added
the
release-note-none
k8s-ci-robot
added
the
cncf-cla: yes
k8s-ci-robot
added
approved
|
/test ? |
|
@prksu: The following commands are available to trigger 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-digitalocean-capi-e2e |
|
@cpanato: The following test failed, say
Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR. 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. I understand the commands that are listed here. |
There was a problem hiding this comment.
seem these changes broke our capi-e2e test.
never mind, capi-e2e test is an optional test.
/lgtm
k8s-ci-robot
added
the
lgtm
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: cpanato, prksu 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 |
|
let me follow up on that, will open a new PR to check this |
|
ahh this is the capi test, will check that |
What this PR does / why we need it:
Using the release CAPI artifacts, the images was not published so that was failing, now it is live and we can use the released artifacts
/assign @prksu @timoreimann @MorrisLaw
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 #
Special notes for your reviewer:
Documentation:
Release note: