Update nodes to Amazon Linux 2023.

[sengi]

This gets us kernel 6 as well as a bunch of other good stuff.

https://docs.aws.amazon.com/linux/al2023/ug/compare-with-al2.html

https://aws.amazon.com/blogs/containers/amazon-eks-optimized-amazon-linux-2023-amis-now-available/

[sengi]

{"level":"info","ts":"2024-04-08T16:21:26Z","msg":"version","GitVersion":"v2.7.2","GitCommit":"fb6460383b75e937e24548e69b6732f49b88755c","BuildDate":"2024-03-22T21:39:56+0000"}
{"level":"error","ts":"2024-04-08T16:21:29Z","logger":"setup","msg":"unable to initialize AWS cloud","error":"failed to introspect vpcID from EC2Metadata or Node name, specify --aws-vpc-id instead if EC2Metadata is unavailable: failed to fetch VPC ID from instance metadata: EC2MetadataError: failed to make EC2Metadata request\n\n\tstatus code: 401, request id: "}

Oh what a lovely surprise. Thanks, Amazon 🙃 https://kubernetes-sigs.github.io/aws-load-balancer-controller/v2.7/deploy/installation/#using-the-amazon-ec2-instance-metadata-server-version-2-imdsv2

I guess I'd better go figure out how to update the launch template.

[sengi]

Or maybe let's just set --aws-region and --aws-vpc-id and get rid of the somewhat surprising dependency on the instance metadata service. Getting the VPC ID into the cluster neatly might be a pain. Let's find out.

[sengi]

Looks good in production so far.