update eksd 1.24 to 1.24.6

[rcrozean]

Issue number:

Closes #2689

Description of changes:
Update kubernetes, etcd, and cloud controller manager versions.

Testing done:

Terms of contribution:

By submitting this pull request, I agree that this contribution is dual-licensed under the terms of both the Apache License, version 2.0, and the MIT license.

[etungsten]

Build aws-k8s-1.24 without problem and launched a few nodes with the AMI in my 1.24 EKS cluster:

$ kubectl get nodes -A -o wide
NAME                                           STATUS   ROLES    AGE    VERSION               INTERNAL-IP      EXTERNAL-IP    OS-IMAGE                                KERNEL-VERSION   CONTAINER-RUNTIME
ip-192-168-21-136.us-west-2.compute.internal   Ready    <none>   106s   v1.24.9-eks-4f83af2   192.168.21.136   35.85.46.224   Bottlerocket OS 1.12.0 (aws-k8s-1.24)   5.15.59          containerd://1.6.12+bottlerocket
ip-192-168-31-168.us-west-2.compute.internal   Ready    <none>   2m1s   v1.24.9-eks-4f83af2   192.168.31.168   35.87.99.186   Bottlerocket OS 1.12.0 (aws-k8s-1.24)   5.15.59          containerd://1.6.12+bottlerocket

Pods get scheduled and running on the nodes fine:

$ kubectl get pods -A
NAMESPACE      NAME                                               READY   STATUS    RESTARTS   AGE
default        csi-secrets-store-secrets-store-csi-driver-9dgqg   3/3     Running   0          14m
default        csi-secrets-store-secrets-store-csi-driver-dfgrt   3/3     Running   0          15m
dns-5592       dns-test-856b62c5-2181-4f3e-b26c-156bf755242f      3/3     Running   0          3m57s
kube-system    aws-node-b6kxw                                     1/1     Running   0          15m
kube-system    aws-node-qlmk7                                     1/1     Running   0          15m
kube-system    coredns-559b5db75d-7nmqk                           1/1     Running   0          14d
kube-system    coredns-559b5db75d-7sbkq                           1/1     Running   0          14d
kube-system    ebs-csi-controller-985774447-q65x9                 6/6     Running   0          14d
kube-system    ebs-csi-controller-985774447-qlz4c                 6/6     Running   0          14d
kube-system    ebs-csi-node-29k6g                                 3/3     Running   0          14m
kube-system    ebs-csi-node-4g2zv                                 3/3     Running   0          15m
kube-system    kube-proxy-dsd44                                   1/1     Running   0          15m
kube-system    kube-proxy-ngvt2                                   1/1     Running   0          15m
secrets-8430   pod-secrets-8b80dee4-b84e-4660-9a80-5b90fa765b0b   3/3     Running   0          44s
sonobuoy       sonobuoy                                           1/1     Running   0          8m15s
sonobuoy       sonobuoy-e2e-job-f63f5980167a45bb                  2/2     Running   0          8m12s

[stmcginnis]

Built and deployed cluster. Looks good:

$ k --kubeconfig /tmp/br124.kubeconfig get nodes -o wide
NAME                                          STATUS   ROLES    AGE    VERSION               INTERNAL-IP     EXTERNAL-IP     OS-IMAGE                                KERNEL-VERSION   CONTAINER-RUNTIME
ip-192-168-52-51.us-east-2.compute.internal   Ready    <none>   103s   v1.24.9-eks-4f83af2   192.168.52.51   52.15.113.223   Bottlerocket OS 1.12.0 (aws-k8s-1.24)   5.15.59          containerd://1.6.12+bottlerocket
$ k --kubeconfig /tmp/br124.kubeconfig apply -f ../testing/test-pod.yaml 
pod/webserver created
$ k --kubeconfig /tmp/br124.kubeconfig get pod -A
NAMESPACE     NAME                       READY   STATUS    RESTARTS   AGE
default       webserver                  1/1     Running   0          6m5s
kube-system   aws-node-lv9h4             1/1     Running   0          7m58s
kube-system   coredns-5c5677bc78-h2mdh   1/1     Running   0          17m
kube-system   coredns-5c5677bc78-hc9t4   1/1     Running   0          17m
kube-system   kube-proxy-jtjf7           1/1     Running   0          7m58s