✨refactor: update to use new community ami account#5133
✨refactor: update to use new community ami account#5133k8s-ci-robot merged 3 commits intokubernetes-sigs:mainfrom
Conversation
|
/test pull-cluster-api-provider-aws-test |
nrb
left a comment
There was a problem hiding this comment.
/lgtm
Looks good, one question on supported versions but it's not a blocker by any means.
d9ec853 to
da36f7e
Compare
|
Until #5138 merges and AMIs are published: /hold |
da36f7e to
d421a43
Compare
50cc6c3 to
1ec7f47
Compare
|
/unhold |
|
/test ? |
|
@richardcase: The following commands are available to trigger required jobs:
The following commands are available to trigger optional jobs:
Use
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. |
|
I'm hoping the e2e will pass now 🤞 /test pull-cluster-api-provider-aws-e2e |
|
/test pull-cluster-api-provider-aws-e2e |
|
Excellent, its using the new AMIs: |
30d00c5 to
29e991b
Compare
|
/test pull-cluster-api-provider-aws-e2e |
3 similar comments
|
/test pull-cluster-api-provider-aws-e2e |
|
/test pull-cluster-api-provider-aws-e2e |
|
/test pull-cluster-api-provider-aws-e2e |
|
The e2e tests are passing 🎉 I have created 5169 to re-enable 3 tests that have been disabled. |
damdo
left a comment
There was a problem hiding this comment.
Great work here @richardcase
Thanks for working hard on this!
/lgtm
/assign @AndiDog @dlipovetsky @Ankitasw @nrb
For approval
|
Also, should we cherry pick this so we can do a v2.6.2 release? |
|
Yeah +1 for that |
|
/cherrypick release-2.6 |
|
@richardcase: once the present PR merges, I will cherry-pick it on top of release-2.6 in a new PR and assign it to you. 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. |
|
@richardcase does this one also close #5161 ? |
Yes it does, thanks @damdo for thinking of that. I have updated the description. |
|
/approve |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: nrb 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 |
|
@richardcase: #5133 failed to apply on top of branch "release-2.6": 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. |
What type of PR is this?
/kind bug
What this PR does / why we need it:
Updates to the project to start using the new CNCF owned AWS account for publishing AMIs. The code has had the old VMWare account removed and the new account ID added. Additionally the docs have been updated including clarifying that the public AMIs should only be used for non-production usage.
Which issue(s) this PR fixes (optional, in
fixes #<issue number>(, fixes #<issue_number>, ...)format, will close the issue(s) when PR gets merged):Relates #5131
Relates #4984
Fixes #5161
Special notes for your reviewer:
A new GitHub Actions workflow (see #5138 ) can be invoked to publish new images. Also #5169 will be done as a follow-up.
Checklist:
Release note: