Updated Kubernetes version to 1.23.16

[danbudris]

Issue number:

Closes #

Description of changes:

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]

Built aws-k8-1.23 AMI and the nodes join cluster and runs pods as expected:

$ kubectl get nodes -o wide
NAME                                           STATUS   ROLES    AGE    VERSION                INTERNAL-IP      EXTERNAL-IP     OS-IMAGE                                KERNEL-VERSION   CONTAINER-RUNTIME
ip-192-168-20-111.us-west-2.compute.internal   Ready    <none>   104s   v1.23.16-eks-ac99dab   192.168.20.111   35.86.251.140   Bottlerocket OS 1.12.0 (aws-k8s-1.23)   5.10.157         containerd://1.6.15+bottlerocket
ip-192-168-4-51.us-west-2.compute.internal     Ready    <none>   3m5s   v1.23.16-eks-ac99dab   192.168.4.51     35.89.21.34     Bottlerocket OS 1.12.0 (aws-k8s-1.23)   5.10.157         containerd://1.6.15+bottlerocket
$ kubectl get pods -A -o wide
NAMESPACE     NAME                                               READY   STATUS    RESTARTS   AGE     IP               NODE                                           NOMINATED NODE   READINESS GATES
default       csi-secrets-store-secrets-store-csi-driver-pzmn9   3/3     Running   0          2m48s   192.168.29.9     ip-192-168-4-51.us-west-2.compute.internal     <none>           <none>
default       csi-secrets-store-secrets-store-csi-driver-zhldj   3/3     Running   0          87s     192.168.3.45     ip-192-168-20-111.us-west-2.compute.internal   <none>           <none>
kube-system   aws-node-d8sxn                                     1/1     Running   0          3m19s   192.168.4.51     ip-192-168-4-51.us-west-2.compute.internal     <none>           <none>
kube-system   aws-node-q2s7h                                     1/1     Running   0          118s    192.168.20.111   ip-192-168-20-111.us-west-2.compute.internal   <none>           <none>
kube-system   coredns-559b5db75d-5t6dt                           1/1     Running   0          35d     192.168.13.30    ip-192-168-4-51.us-west-2.compute.internal     <none>           <none>
kube-system   coredns-559b5db75d-b7bcz                           1/1     Running   0          35d     192.168.4.125    ip-192-168-4-51.us-west-2.compute.internal     <none>           <none>
kube-system   ebs-csi-controller-985774447-78qdq                 6/6     Running   0          35d     192.168.15.87    ip-192-168-4-51.us-west-2.compute.internal     <none>           <none>
kube-system   ebs-csi-controller-985774447-jb2zc                 6/6     Running   0          35d     192.168.4.47     ip-192-168-4-51.us-west-2.compute.internal     <none>           <none>
kube-system   ebs-csi-node-8qz2s                                 3/3     Running   0          2m48s   192.168.28.1     ip-192-168-4-51.us-west-2.compute.internal     <none>           <none>
kube-system   ebs-csi-node-mqrgp                                 3/3     Running   0          87s     192.168.8.184    ip-192-168-20-111.us-west-2.compute.internal   <none>           <none>
kube-system   kube-proxy-5xn4v                                   1/1     Running   0          118s    192.168.20.111   ip-192-168-20-111.us-west-2.compute.internal   <none>           <none>
kube-system   kube-proxy-qsv7n                                   1/1     Running   0          3m19s   192.168.4.51     ip-192-168-4-51.us-west-2.compute.internal     <none>           <none>

[stmcginnis]

Looks good to me:

$ k get nodes
NAME                                           STATUS   ROLES    AGE   VERSION
ip-192-168-70-189.us-east-2.compute.internal   Ready    <none>   48m   v1.23.16-eks-ac99dab

$ k get all -A
NAMESPACE     NAME                           READY   STATUS    RESTARTS   AGE
kube-system   pod/aws-node-s9nqk             1/1     Running   0          48m
kube-system   pod/coredns-5948f55769-kcqrl   1/1     Running   0          59m
kube-system   pod/coredns-5948f55769-vrbld   1/1     Running   0          59m
kube-system   pod/kube-proxy-5grmk           1/1     Running   0          48m

NAMESPACE     NAME                 TYPE        CLUSTER-IP    EXTERNAL-IP   PORT(S)         AGE
default       service/kubernetes   ClusterIP   10.100.0.1    <none>        443/TCP         59m
kube-system   service/kube-dns     ClusterIP   10.100.0.10   <none>        53/UDP,53/TCP   59m

NAMESPACE     NAME                        DESIRED   CURRENT   READY   UP-TO-DATE   AVAILABLE   NODE SELECTOR   AGE
kube-system   daemonset.apps/aws-node     1         1         1       1            1           <none>          59m
kube-system   daemonset.apps/kube-proxy   1         1         1       1            1           <none>          59m

NAMESPACE     NAME                      READY   UP-TO-DATE   AVAILABLE   AGE
kube-system   deployment.apps/coredns   2/2     2            2           59m

NAMESPACE     NAME                                 DESIRED   CURRENT   READY   AGE
kube-system   replicaset.apps/coredns-5948f55769   2         2         2       59m

$ k apply -f ../testing/test-pod.yaml 
pod/webserver created
$ k get pod
NAME        READY   STATUS    RESTARTS   AGE
webserver   1/1     Running   0          7s