kubernetes-sigs
[release-2.6] ✨refactor: update to use new community ami account
What type of PR is this?
/kind bug
What this PR does / why we need it:
Manual cherry-pick of #5133
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
Special notes for your reviewer:
Checklist:
- [ ] squashed commits
- [ ] includes documentation
- [ ] includes emojis
- [ ] adds unit tests
- [ ] adds or updates e2e tests
Release note:
action required
A new community owned AWS account is now being used for publishing AMIs. The old account owner by a company is no longer accessible and the images are being automatically deleted by AWS. Support for ubuntu 18.04 & 20.04 has been dropped and ubuntu 24.04 is now the default OS if no OS is supplied.
[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: Once this PR has been reviewed and has the lgtm label, please ask for approval from richardcase. For more information see the Kubernetes Code Review Process.
The full list of commands accepted by this bot can be found here.
Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment
@richardcase: The following commands are available to trigger required jobs:
-
/test pull-cluster-api-provider-aws-build -
/test pull-cluster-api-provider-aws-build-docker
Use /test all to run all jobs.
In response to this:
/test ?
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: The following commands are available to trigger required jobs:
-
/test pull-cluster-api-provider-aws-build -
/test pull-cluster-api-provider-aws-build-docker -
/test pull-cluster-api-provider-aws-build-docker-release-2-6 -
/test pull-cluster-api-provider-aws-build-release-2-6 -
/test pull-cluster-api-provider-aws-test-release-2-6 -
/test pull-cluster-api-provider-aws-verify-release-2-6
The following commands are available to trigger optional jobs:
-
/test pull-cluster-api-provider-aws-apidiff-release-2-6 -
/test pull-cluster-api-provider-aws-e2e-blocking-release-2-6 -
/test pull-cluster-api-provider-aws-e2e-conformance-release-2-6 -
/test pull-cluster-api-provider-aws-e2e-conformance-with-ci-artifacts-release-2-6 -
/test pull-cluster-api-provider-aws-e2e-eks-gc-release-2-6 -
/test pull-cluster-api-provider-aws-e2e-eks-release-2-6 -
/test pull-cluster-api-provider-aws-e2e-eks-testing-release-2-6 -
/test pull-cluster-api-provider-aws-e2e-release-2-6
Use /test all to run the following jobs that were automatically triggered:
-
pull-cluster-api-provider-aws-apidiff-release-2-6 -
pull-cluster-api-provider-aws-build -
pull-cluster-api-provider-aws-build-docker -
pull-cluster-api-provider-aws-build-docker-release-2-6 -
pull-cluster-api-provider-aws-build-release-2-6 -
pull-cluster-api-provider-aws-test-release-2-6 -
pull-cluster-api-provider-aws-verify-release-2-6
In response to this:
/test ?
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: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:
| Test name | Commit | Details | Required | Rerun command |
|---|---|---|---|---|
| pull-cluster-api-provider-aws-e2e-release-2-6 | 4171551573a19c75c07362629dac5f89620630ab | link | false | /test pull-cluster-api-provider-aws-e2e-release-2-6 |
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-sigs/prow repository. I understand the commands that are listed here.
I think we can consider closing this and just going with a v2.7.0 release. Until we decide:
/hold
@richardcase: Closed this PR.
In response to this:
As v2.7.1 is out:
/close
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.