Skip to content

Commit 50cc6c3

Browse files
committed
stuff
Signed-off-by: Richard Case <[email protected]>
1 parent 9c03a1c commit 50cc6c3

File tree

2 files changed

+7
-6
lines changed

2 files changed

+7
-6
lines changed

README.md

Lines changed: 1 addition & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -46,8 +46,7 @@ cluster on AWS.
4646

4747
- Native Kubernetes manifests and API
4848
- Manages the bootstrapping of VPCs, gateways, security groups and instances.
49-
- Choice of Linux distribution among Amazon Linux 2, CentOS 7, Ubuntu and Flatcar
50-
using [pre-baked AMIs][published_amis].
49+
- Choice of Linux distribution using [pre-baked AMIs][published_amis].
5150
- Deploys Kubernetes control planes into private subnets with a separate
5251
bastion server.
5352
- Doesn't use SSH for bootstrapping nodes.

docs/book/src/topics/images/built-amis.md

Lines changed: 6 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -5,22 +5,24 @@ New AMIs are built on a best effort basis when a new Kubernetes version is relea
55
## AMI Publication Policy
66

77
- AMIs should only be used for non-production usage. For production environments we recommend that you build and maintain your own AMIs using the image-builder project.
8-
- AMIs will only be published for the latest release series and 2 previous release series. For example, if the current release series is v1.31 then AMIs will only be published for v1.31.x, v1.30.x, v1.29.x.
9-
- When there is a new k8s release series then any AMIs no longer covered by the previous point will be deleted. For example, when v1.32.0 is pubslished then any AMIs for the v1.29 release series will be deleted.
8+
- AMIs will only be published for the latest release series and 2 previous release series. For example, if the current release series is v1.30 then AMIs will only be published for v1.30, v1.29, v1.28.
9+
- When there is a new k8s release series then any AMIs no longer covered by the previous point will be deleted. For example, when v1.31.0 is published then any AMIs for the v1.28 release series will be deleted.
1010
- Existing AMIs are not updated for security fixes and it is recommended to always use the latest patch version for the Kubernetes version you want to run.
1111

12+
> NOTE: As the old community images where located in an AWS account that the project no longer has access to and because those AMIs have been automatically deleted we have started publishing images again from v1.29.9
13+
1214
## Finding AMIs
1315

1416
`clusterawsadm ami list` command lists pre-built reference AMIs by Kubernetes version, OS, or AWS region. See [clusterawsadm ami list](https://cluster-api-aws.sigs.k8s.io/clusterawsadm/clusterawsadm_ami_list.html) for details.
1517

1618
If you are using a version of clusterawsadm prior to v2.6.2 then you will need to explicitly specify the owner-id for the community account: `clusterawsadm ami list --owner-id 819546954734`.
1719

1820
## Supported OS Distributions
19-
- Amazon Linux 2 (amazon-2)
2021
- Ubuntu (ubuntu-22.04, ubuntu-24.04)
21-
- Centos (centos-7)
2222
- Flatcar (flatcar-stable)
2323

24+
> Note: Centos (centos-7) and Amazon Linux 2 (amazon-2) where supported but there are some issues with the AMI build that need fixing.
25+
2426
## Supported AWS Regions
2527
- ap-northeast-1
2628
- ap-northeast-2

0 commit comments

Comments
 (0)